On Mon, 20 Jun 2005, der Mouse wrote:
> (The real problem, of course, is not just this one instance, but more
> generally the gcc maintainers assuming that semantics undefined by
> the standard have not been defined by any gcc target - like what our
> printf does, or at least used to do, with nil pointers, printing them
> as (null).)

It sounds as though gcc should grow some options to
allow it to differentiate between <standard> and
<standard>-as-extended-by-<organisation>-<version>.  Until that
happens, if you use "gcc -std=C99" to tell the compiler that your code
was written in C99, you should not be surprised that the compiler
believed you, and that you do not get the C99-as-extended-by-NetBSD-2.0
semantics.

--apb (Alan Barrett)