> -----Original Message----- > From: John Myers [mailto:[email protected]] > Sent: Sunday, February 27, 2011 9:45 PM > To: Weddington, Eric > Cc: [email protected] > 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. Eric _______________________________________________ AVR-libc-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
