Re: [Chicken-hackers] Pessimizing undefined behavior

[felix . winkelmann]

>
> Nothing changes if we statically assign these values, the user still
> cannot rely on undefined to be either true or false.

Once you give a fixed meaning, even by doing an optimization based
on this meaning, users _will_ start to rely on it. At that stage it isn't
undefined anymore.

> > Sure, that could even be considered a benefit. Yet, I'd rather see removing
> > the "undefined" status altogether from forms like that than make it mean 
> > something
> > specific in some specific cicumstances.
>
> I don't understand this. What do you mean by "removing undefined
> status"?

Return a defined value in all cases.


felix