[1570] in Kerberos_V5_Development
Re: lib/rpc breaks on non-ANSI compilers
daemon@ATHENA.MIT.EDU (Sam Hartman)
Tue Aug 13 22:17:16 1996
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: "Barry Jaspan" <bjaspan@MIT.EDU>, tlyu@MIT.EDU, krbdev@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 13 Aug 1996 22:17:05 -0400
In-Reply-To: "Theodore Y. Ts'o"'s message of Tue, 13 Aug 1996 21:36:37 -0400
>>>>> ""Theodore" == "Theodore Y Ts'o" <tytso@MIT.EDU> writes:
"Theodore> My general feeling as far as non-ANSI C support is that
"Theodore> (a) we shouldn't go out of our way to NOT support ANSI
"Theodore> C, but (b) we shouldn't go out of our to break K&R
"Theodore> support, either.
"Theodore> If a Kerberos developer wants to make things work under
"Theodore> Ultrix cc or SunOS suncc, that's fine, as long as the
"Theodore> changes aren't too bletcherous. To quote from the GNU
"Theodore> Coding Standards:
Is it reasonable to assume that once enough ansi-isms make
their way into components of the distribution that you can't really
have a useful Kerberos implementation without using an Ansi compiler,
we drop all future attempts at K&R support?
--Sam
