> The __P has the definite down side that it looks ugly, and that in some
> cases a compiler not-gcc may complain if the K&R style definition means
> a different thing than the prototype;
> int foo(short);
> followed by
> int foo(x)
> 	short x;
> {
> ...
> }

Why do you use "int foo(short);" in this case ?
It should be "int foo(int);", because K&R style function definition
makes short argument to be promoted to int.
(and "int foo(short)" MAY make short argument to be passed as short, not int)
--
soda@sra.co.jp