[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
At 4:41 AM 1/12/96, Pip wrote:
>> the value as Null for the first, Mull for the second, Lull for the
>> third, and so on....Any ideas?
>Apparantly, this is a known bug which will not get fixed by release
Here's more on this from Brendan Eich, in response to a message reporting
>What an amusing bug -- it aflicts window.alert(), window.confirm(), and
>window.prompt(). If any of them are passed null as an argument, their
>evil native C code implementations turn it into a string but leave the
>interpreter thinking it's still of object type. The dereference that
>ensues has predictable results, although on big-endian machines you get
>null, nulk, nulj, ...
>This won't get fixed for 2.0, so beware. Thanks for finding it!
As for your other question:
>I tried finding the news message that went into a little detail
>about it, but couldn't get _anything_ out of the
>netscape.devs-livescript news group where I think it appeared. I'll try
The name of the newsgroup was changed from netscape.devs-livescript to
messages still there (i.e., if you select "Show All Messages" from the
Frank Hecker Pre-sales tech support, Netscape field sales group