[parenscript-devel] Equality issues

Daniel Gackle danielgackle at gmail.com
Tue Apr 20 02:15:51 UTC 2010

The array literals fix worked, thanks. Next up: the changes around equality
are a problem.

Specifically, the NULL operator, which used to evaluate to true on both null
and undefined, now applies strict equality, meaning that (null undefined) is
false. Since we use the NULL operator in a great many places precisely to
check whether something is null or undefined, this change breaks our code.
In general, I've found it to be good to conflate null and undefined in most
of our PS code; it simplifies things and works fine. So I guess we have to
go on record as protesting this change... especially since there already
existed ways to distinguish null from undefined in the minority case when
it's needed.

Others' thoughts?


p.s. I haven't looked closely at the other implications of the equality
changes, because the NULL issue is such a big one that I thought I'd start
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/parenscript-devel/attachments/20100419/88778e9b/attachment.html>

More information about the parenscript-devel mailing list