Re: RFC: status icon support

[Andreas Schwab <schwab@suse.de>]

David Kastrup <dak@gnu.org> writes:

> Andreas Schwab <schwab@suse.de> writes:
>
>> David Kastrup <dak@gnu.org> writes:
>>
>>> Richard Stallman <rms@gnu.org> writes:
>>>
>>>>     Please no K&R in new code.  
>>>>
>>>> We have no policy against K&R style.  I recently accepted non-K&R
>>>> function definitions in Emacs sources, but I still do not particularly
>>>> like it.  K&R style is easier to read anyway.
>>>
>>> It stops the compiler from doing type checking and type conversions, for
>>> one thing.
>>
>> Unless you add prototypes.
>
> In which case you have
> a) undefined behavior (the compiler need not check whether the prototype
>    matches the function declaration).

There is nothing undefined in old-style function defintions.

> b) not K&R compatible C, so where is the point?

The Emacs sources use macros that keep prototypes from being visible
from obsolte compilers.  What's your point?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."