🚀 go-pugleaf

The gcc documentation states:
> If the compiler does not produce an error message for invalid 
> input, that is a compiler bug. However, you should note that 
> your idea of "invalid input" might be my idea of "an extension"
> or "support for traditional practice".

Is this a bug?  Or is it "support for traditional practice"?

carbon% head static*.c
==> static_bug.c <==
static const char foo[];

int
main(int argc, const char *argv[]) {
  printf("foo = '%s'\n",foo);
  return 0;
}

#ifdef DEFINE_IT
static const char foo[] = "bar";
#endif

==> static_bug2.c <==
const char foo[] = "baz";
carbon% gcc static*.c
carbon% a.out
foo = 'baz'
carbon% gcc -DDEFINE_IT static*.c
carbon% a.out
foo = 'bar'

The above happens on 
GNU C version 2.6.3 (sparc) compiled by GNU C version 2.6.3.
running on
SunOS carbon 5.5 Generic sun4m sparc SUNW,SPARCstation-20
and identically on
GNU C version 2.7.2 [AL 1.1, MM 40] SGI running IRIX 5.x compiled by CC.
running on 
IRIX archimedes 5.3 11091810 IP17 mips.

The IRIX C compiler gives an error:

archimedes 23% cc static*.c
static_bug.c:
cfe: Error: static_bug.c, line 1: storage size for 'foo' isn't known
 static const char foo[];
 ------------------^

--
huffe@carbon.chem.nyu.edu (Edward J. Huff) 212-998-8465