On Wednesday 23 September 2009 21:14, Joerg Wunsch wrote: > Ruud Vlaming <r...@betaresearch.nl> wrote: > > > I noticed a strange behaviour when you place a zero length array in > > 'nocommon'. > > No idea why the behaviour changes, but as a note of warning: a > zero-length array is not allowed by the C standard. Well, mayby not in ISO C, but certainly in GNU C: http://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html thus at least the gcc compiler should be able to handle it :-)
> No idea what you are trying to achieve here though. Although the link gives an example how this could be usefull, i found a different application. I configure my projects using preprop defines, and if a don't need an array internally, the size calculation simply produces a zero. That way no space is taken, and it is much easier than having if-defs around all arrays to see if they accedently have size zero. But it seems it does not work when they are not in the common space. This 'quirk' of gcc does not seem to be specifically avr related but probably we are the only one's left to care about the spoilled byte. Ruud. _______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
