🚀 go-pugleaf

The following (meaningless) two-line program does not get a warning when
compiled with -Wall on a 486 running Interactive Unix (configured as
`--with-gnu-as i386-isc').  (I doubt this is a machine-dependent
phenomenom.)

static void foo ();
void foo () { foo (); }

bash$ gcc -v -c -Wall /tmp/test.c
Reading specs from /usr/local/gnu/lib/gcc-lib/i386-isc/2.2.2/specs
gcc version 2.2.2
 /usr/local/gnu/lib/gcc-lib/i386-isc/2.2.2/cpp -lang-c -v -undef -D__GNUC__=2 -Dunix -Di386 -D__unix__ -D__i386__ -D__unix -D__i386 -Wall /tmp/test.c /tmp/cca04478.i
GNU CPP version 2.2.2 (80386, BSD syntax)
 /usr/local/gnu/lib/gcc-lib/i386-isc/2.2.2/cc1 /tmp/cca04478.i -quiet -dumpbase test.c -Wall -version -o /tmp/cca04478.s
GNU C version 2.2.2 (80386, BSD syntax) compiled by GNU C version 2.2.1.
 /usr/local/gnu/lib/gcc-lib/i386-isc/2.2.2/as -o test.o /tmp/cca04478.s
bash$ 

Since having the `static' on only the definition provokes a warning, I
expected the converse -- having `static' only on the declaration -- to do
so also.

Apologies if I missed this in the documentation.

karl@cs.umb.edu