As Jan Waclawek wrote: > Just want to remark that these issues had been discussed already in > the thread stemming from > http://lists.nongnu.org/archive/html/avr-libc-dev/2011-09/msg00025.html > ...
And the outcome was that the macro solution is not really suitable as a replacement. To quote Johann: > prog_char as a macro is dreaded. > const prog_char * const p = NULL; > puts p in progmem so it's broken by design. With that users will be > taken for a ride. I agree that having typedefs for the named address space implementation might be a good thing. They should probably start with flash_ (rather than prog_) then, to clearly indicate they are *different*, and need a different usage. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
