[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] Progmem types compatibility
From: |
Jan Waclawek |
Subject: |
Re: [avr-libc-dev] Progmem types compatibility |
Date: |
Tue, 10 Jan 2012 10:46:17 +0100 |
>I am really not sure. There is no read use of such a type, it's just because
>some guys are to lazy to type some letters. Moreover in the case of pointers,
>you have the difference between pointers, const pointers, pointers to const and
>const pointers to const etc. and all for arbitrary number of types and other
>qualifiers like volatile, signed or unsigned.
>
>For the matter of clearness I'd discourage such code obfuscation, there is no
>real benefit.
Couldn't the same be said of *any* typedef? Or macro? Or, for that matter,
functions, which too serve to spare some typing and potentially obfuscate
things?
JW
- Re: [avr-libc-dev] Progmem types compatibility, (continued)
- Re: [avr-libc-dev] Progmem types compatibility, David Brown, 2012/01/09
- Re: [avr-libc-dev] Progmem types compatibility, Dmitry, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility, Joerg Wunsch, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility, David Brown, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility, Joerg Wunsch, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility, Jan Waclawek, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility, Joerg Wunsch, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility, David Brown, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility, Jan Waclawek, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility, Georg-Johann Lay, 2012/01/10
- Re: [avr-libc-dev] Progmem types compatibility,
Jan Waclawek <=
- Re: [avr-libc-dev] Progmem types compatibility, David Brown, 2012/01/10