Subject: Re: C Language Standard(s)
To: Simon J. Gerraty <>
From: matthew green <>
List: current-users
Date: 01/10/1996 14:12:24
   > The __P has the definite down side that it looks ugly, 
   But less ugly than 
   #ifdef __STDC__
   int foo(short x)
   int foo(x) short x;

but how *else* do you do this correctly, for it to work with both
k&r compilers and "strict ansi" ones ?

i know it's ugly, but, i know of no other way to get the benefits
of prototypes while still allowing the code to compile with non-ansi
compilers (which some code that i maintain requires).


(ps, i use _ rather than __P -- it's much less ugly  :-)