🚀 go-pugleaf

lmiller@aero.org (Lawrence H. Miller) writes:

>If I have a static function defined in a file, must the 
>prototype also have the word static?  My reading of the
>standard is that the word static is forbidden in block
>scope declarations, but gnu C requires it.

I can't reproduce the problem that you describe.  Given the program

	void f(void) { static void g(void); g(); }
	static void g(void) {}

`gcc -ansi -pedantic' (GCC 2.2.2) issues a diagnostic, as required by
the C standard:

	t.c: In function `f':
	t.c:1: warning: invalid storage class for function `g'

The proper way to write this is:

	static void g(void);
	void f(void) { g(); }
	static void g(void) {}


It's not necessarily a good idea to use GCC to check for conformance.
The GCC manual says:

     Some users try to use `-pedantic' to check programs for strict ANSI
     C conformance.  They soon find that it does not do quite what they
     want: it finds some non-ANSI practices, but not all--only those
     for which ANSI C *requires* a diagnostic.