>>>>> "Simon" == "Simon J Gerraty" <sjg@zen.void.oz.au> writes:

Simon> What does anyone think it is costing - using the old style
Simon> definitions?  Why change something that is not broken?

Precisely.  When importing new code into the system (be it user-level or
kernel level), why change new-style function definitions to old ones,
particularly in cases where there are no narrow types that might cause
confusion?

(This *has* happened on imported code.)

For totally new code, I see no reason to insist on changing it to
"classic K&R" style function definitions.

==John