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? Jan > >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 >alternative. > >If someone should discover that replacing them with macros are deemed safe, >then a patch should be provided. > >Eric _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
