On Apr 7, 2005, at 1:40 PM, Michael G Schwern wrote:
Zee goggles, zey do nothing!!!
I thought I eliminated the radiation...
Not so different, that's what I would have done were it not for the fact
that it alters caller(). If Javascript has no such problems then do it,
but I suspect it does.
I have no idea whether JavaScript even has the concept of caller(). I need to find that out, though, because right now all errors are reported in package '', file '', line 0. I'd really love to know how to get at that data.
if( !condition ) {
skip(because, number);
}
else {
...test...
}
Makes sense; that's what Ovid suggested, too. So I'll probably do that.
Could object destruction be used somehow?
That'd be nice, but I can't see how to plug into that in JavaScript. Besides, I think that global objects are only destroyed when you leave a page, not when code finishes executing.
My only other note in glancing over this is to not make the mistake of
parroting eq*, ie. functions which are not tests. Proceed directly to
isDeeply() if possible. If its not possible, if the function prototypes
in Javascript won't allow something like isDeeply() then make the eq*
functions real tests such that later isDeeply() style diagnostics can be
added.
Well, right now, isDeeply() should do the right thing. I could just comment out the eqArray() and eqAssoc() functions, or make them tests, too. That'd be pretty easy to do, actually.
Regards,
David
