Olly> I'm unsure how `int a[0];' will be handled by various compilers.
Tom> gcc accepts this as an extension. It is useful when using the
Tom> "struct hack", at least.
Akim> I don't understand what you are referring to. Could you give details?
In C you can write something like this:
struct foo
{
int fixed_part;
char buffer[1];
}
Then when you allocate a "foo" you over-allocate, and use "buffer" as
a string -- you assume that your over-allocated parts immediately
follow "buffer".
Paul says the current C standard doesn't allow this, but I thought
there was a special exception precisely to allow it. Anyway, it is a
very common practice.
Tom
- Re: Patch to avoid unnecessary uses of AC_TRY_RUN Olly Betts
- Re: Patch to avoid unnecessary uses of AC_TRY_RUN Steve Robbins
- Re: Patch to avoid unnecessary uses of AC_TRY_RUN Alexandre Oliva
- Re: Patch to avoid unnecessary uses of AC_TRY_RUN Earnie Boyd
- Re: Patch to avoid unnecessary uses of AC_TRY_RUN Olly Betts
- Re: Patch to avoid unnecessary uses of AC_TRY_RUN Tom Tromey
- Re: Patch to avoid unnecessary uses of AC_TRY... Olly Betts
- Re: Patch to avoid unnecessary uses of AC... Paul D. Smith
- Re: Patch to avoid unnecessary uses of AC_TRY... Akim Demaille
- Re: Patch to avoid unnecessary uses of AC... Tom Tromey
- Re: Patch to avoid unnecessary uses ... Paul D. Smith
- Re: Patch to avoid unnecessary u... Tom Tromey
- Re: Patch to avoid unnecessary u... Akim Demaille
