🚀 go-pugleaf

In article <n/NIwQ9ytldJ084yn@csn.net>, Thad Smith <ThadSmith@acm.org> wrote:
>In article <3vp60e$o8c@solutions.solon.com>,
>seebs@solutions.solon.com (Peter Seebach) wrote:
>> I think we're disagreeing about the use of "undefined".  The use of
>> an uninitialized float is undefined behavior, right?  So, are you
>> advocating undefined behavior as part of the normal functioning of the
>> routine?  I can see "I don't care what value goes here", I can't see
>> "I want this undefined".
> Intersection coordinates, in the case that there is no
> intersection, is a good example where an undefined return value makes
> sense.

I think the Standard's term that you are both looking for is "unspecified":
the value must be safe to use, but nothing states what it is.

-- 
Clive D.W. Feather                       | If you lie to the compiler,
clive@demon.net        (work, preferred) | it will get its revenge.
clive@stdc.demon.co.uk (home)            |   - Henry Spencer