On Feb 16, 6:39 am, Jason Mulligan <[email protected]>
wrote:
> that's not really valid, undefined is as valuable as null when
> checking an object; just write a handler and drop it onto the array
> prototype.
>
But why would:
if ( d.foo.bar == "yay" ) {
[stuff]
}
preclude
if ( d.foo === undefined ) {
[stuff]
}
? Shouldn't that be easy for the compiler to distinguish? Basically,
if at any depth a key is undefined, then stop going deeper and the
whole thing just evaluates to undefined.
--
To view archived discussions from the original JSMentors Mailman list:
http://www.mail-archive.com/[email protected]/
To search via a non-Google archive, visit here:
http://www.mail-archive.com/[email protected]/
To unsubscribe from this group, send email to
[email protected]
