> -----Original Message----- > From: avr-libc-dev-bounces+eric.weddington=atmel....@nongnu.org > [mailto:avr-libc-dev-bounces+eric.weddington=atmel....@nongnu.org] On > Behalf Of David A. Mellis > Sent: Monday, February 28, 2011 6:14 AM > To: John Myers > Cc: avr-libc-dev@nongnu.org; Weddington, Eric > Subject: Re: [avr-libc-dev] [RFC] Conditional poisoning of deprecated > items > > Alternatively, is there a way to make this the default, but generate > warnings, not errors, for the use of deprecated items? That would > make it clear that people are using something that's been deprecated, > but allow them to ignore the warning and proceed if they wish. Then > there could be an option to disable the warnings, or to turn the > warnings into errors. > > (Or are warnings already generated for deprecated items?) >
That would be good too. Unfortunately, this method is all I've been able to find so far. If someone discovers a different method that would allow these other capabilities, then I think we could easily change the intent. Whatever method is discovered and used, it has to work on C preprocessor macros too. Eric _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
