[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?
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] [bug #33716] pgmspace typedefs not legal, Eric Weddington, 2011/09/26
- [avr-libc-dev] [bug #33716] pgmspace typedefs not legal, Jan Waclawek, 2011/09/26
- Re: [avr-libc-dev] [bug #33716] pgmspace typedefs not legal, Weddington, Eric, 2011/09/26
- Re: [avr-libc-dev] [bug #33716] pgmspace typedefs not legal, Bill Westfield, 2011/09/27
- Re: [avr-libc-dev] [bug #33716] pgmspace typedefs not legal, Georg-Johann Lay, 2011/09/27
- Re: [avr-libc-dev] [bug #33716] pgmspace typedefs not legal, Jan Waclawek, 2011/09/27
- Re: [avr-libc-dev] [bug #33716] pgmspace typedefs not legal, Georg-Johann Lay, 2011/09/27
Re: [avr-libc-dev] [bug #33716] pgmspace typedefs not legal, Georg-Johann Lay, 2011/09/27