[17485] in Kerberos_V5_Development
Re: Proposed platform assumption changes
daemon@ATHENA.MIT.EDU (Sam Hartman)
Mon Jan 30 12:26:53 2012
From: Sam Hartman <hartmans@mit.edu>
To: Nico Williams <nico@cryptonector.com>
Date: Mon, 30 Jan 2012 12:26:36 -0500
In-Reply-To: <CAK3OfOhqP6pJ60tMKivQoS+nOftxs8y4=DBygOrRnAhdM8r2zA@mail.gmail.com>
(Nico Williams's message of "Mon, 30 Jan 2012 10:17:12 -0600")
Message-ID: <tslliopxfsj.fsf@mit.edu>
MIME-Version: 1.0
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
>>>>> "Nico" == Nico Williams <nico@cryptonector.com> writes:
Nico> Second, assuming you have a C99 compiler on some of the
Nico> platforms that you build for (MIT does) you get the benefit of
Nico> safety checking from the compiler. This matters when you have
Nico> several fields of the same type in a struct, which w/o
Nico> designated initializers makes it too easy to assign the wrong
Nico> values to fields.
One significant downside of this macro is that it doesn't catch ordering
problems when built with a c99 compiler. So, if most of your platforms
are c99 but some are not, you can introduce significant lack-of-safety
through minimizing testing of the non-c99 platforms.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
