[1567] in Kerberos_V5_Development
Re: lib/rpc breaks on non-ANSI compilers
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Tue Aug 13 21:36:50 1996
Date: Tue, 13 Aug 1996 21:36:37 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: tlyu@MIT.EDU, krbdev@MIT.EDU
In-Reply-To: Barry Jaspan's message of Mon, 12 Aug 96 20:18:53 -0400,
<9608130018.AA03137@beeblebrox.MIT.EDU>
My general feeling as far as non-ANSI C support is that (a) we shouldn't
go out of our way to NOT support ANSI C, but (b) we shouldn't go out of
our to break K&R support, either.
If a Kerberos developer wants to make things work under Ultrix cc or
SunOS suncc, that's fine, as long as the changes aren't too
bletcherous. To quote from the GNU Coding Standards:
> However, it is easy to support non-ANSI compilers in most programs,
>so you might still consider doing so when you write a program. Instead
>of writing function definitions in ANSI prototype form,
>...
>write the definition in pre-ANSI style like this,
>...
>and use a separate declaration to specify the argument prototype:
>
> You need such a declaration anyway, in a header file, to get the
>benefit of ANSI C prototypes in all the files where the function is
>called. And once you have it, you lose nothing by writing the function
>definition in the pre-ANSI style.
- Ted
