[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: David A. Mellis
Subject: Re: [avr-libc-dev] [RFC] Conditional poisoning of deprecated items
Date: Mon, 28 Feb 2011 08:14:10 -0500

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?)

On Sun, Feb 27, 2011 at 11:44 PM, John Myers <address@hidden> wrote:
> On Sun, Feb 27, 2011 at 8:23 PM, Weddington, Eric <address@hidden
>> wrote:
>> ...
>> I propose that this poisoning be done in avr-libc header files, as needed,
>> using such a conditional define. The default would be to have the poisoning
>> OFF, like above, which allows all deprecated items exist as before. A user
>> would define the symbol above to turn on the poisoning of all deprecated
>> items in avr-libc, for the purpose of discovering and fixing all deprecated
>> items in their application code.
>> I'm not stuck on the name of the conditional define to use. I'm open to
>> better ideas.
>> Thoughts?
>> Eric Weddington
> 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.
> --John
> _______________________________________________
> AVR-libc-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-libc-dev

reply via email to

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