[Top][All Lists]

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

Re: [avr-libc-dev] [bug #33716] pgmspace typedefs not legal

From: Jan Waclawek
Subject: Re: [avr-libc-dev] [bug #33716] pgmspace typedefs not legal
Date: Tue, 27 Sep 2011 09:37:10 +0200

What exactly do you mean by "safe" in this context, and how could that be 
discovered or shown?

The user who wants to declare a variable to be positioned in FLASH (code 
memory), and obeys the deprecation warning, is now presumably recommended to 
write the PROGMEM keyword after the type, e.g. unsigned char PROGMEM.

How exactly could a macro expanding into the same sequence be unsafe?


>Until such time that it can be shown that replacing them with macros is a safe 
>alternative, then they will stay as deprecated, as deprecation is a known safe 
>If someone should discover that replacing them with macros are deemed safe, 
>then a patch should be provided.

reply via email to

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