[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-libc-dev] [RFC] Conditional poisoning of deprecated items

From: Weddington, Eric
Subject: RE: [avr-libc-dev] [RFC] Conditional poisoning of deprecated items
Date: Mon, 28 Feb 2011 06:17:25 -0700

> -----Original Message-----
> From: John Myers [mailto:address@hidden
> Sent: Sunday, February 27, 2011 9:45 PM
> To: Weddington, Eric
> Cc: address@hidden
> Subject: Re: [avr-libc-dev] [RFC] Conditional poisoning of deprecated
> items
> I don't think the type of people that continue to use deprecated symbols
> will bother with using that define either.  I think the default should be
> to have poisoning on.

I would normally agree with that. However, with poisoning on, the macro 
definitions still generate a warning. I don't want to give the user who uses 
all up-to-date features a whole bunch of new warnings just to point out 
deprecated items.

If you can figure out a way to have gcc to only give an error on *usage* of a 
symbol (and not also a warning on the #define) then I think we can certainly do 
what you suggested.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]