🚀 go-pugleaf

barmar@think.com (Barry Margolin) writes:

>Actually, doesn't the standard require that function
>declarations/prototypes and definitions be consistent with each other?  If
>the function is defined with an ANSI parameter list, the caller must have a
>prototype in scope.  If the function is defined with a K&R1 parameter list,
>the caller can use an old-style declaration (or no declaration at all,
>letting it default, if the function returns int).

Not quite.  You are allowed to mix prototype and non-prototype
declarations and definition of the same function, provided the
promotions implied by the non-prototype declaration/definition
do not result in any changes.  In practice, this means not using
any parameters of type char, short, or float.  If enums are smaller
than ints, avoid those too.

Conforming examples:

int foo(int, long, double); /* prototype */

foo(i, l, d) /* implicit int return and int type for 'i' */
long l;
double d;
{ ... }

int bar();	/* declaration */

int bar(int i, long l, double d) /* prototyped header */
{ ... }
-- 

Steve Clamage, TauMetric Corp, steve@taumet.com
Vice Chair, ANSI C++ Committee, X3J16