strange "||" behavior in JUM tests and jum.debug()

[alex]

attached test runner file outputs:

obelisk:/tmp alex$ rhino tmp.js js: "/Users/alex/projects/dojo/trunk/tests/prologue.js", line 6: Couldn't open file "../src/bootstrap1.js". js: "/Users/alex/projects/dojo/trunk/tests/prologue.js", line 8: Couldn't open file "../src/hostenv_rhino.js". js: "/Users/alex/projects/dojo/trunk/tests/prologue.js", line 10: Couldn't open file "../src/bootstrap2.js". (jsunit_wrap.js) got 1 test function names INFO: no setTimeout, not checking async completion (jsunit_wrap.js) no setTimeout, not checking async completion TEST: There are 1 test groups... TEST: group 'foo' has 1 tests to run... TEST: test 'bar' ... 4 DEBUG: true TEST: FAILED test 'foo.bar': assertEquals(foo) failed: expected |(new Number(4))| (typeof=number), but got |(new Boolean(true))| (typeof=boolean) TEST: ======================= TEST: Total tests: 1 TEST: Failed: 1 TEST: Error: 0 TEST: Skipped: 0 TEST: Passed: 0

When i should output "3" instead of "true" and the test should pass

[alex]

this appears to be related to a core language bug in Rhino, which I don't think is fixable for 0.2, and not something we should block on. I've updated the source files and the tests not to use "

" in the offending locations, so we'll mark this closed but keep an eye on it.

[(none)]

Milestone 0.2release deleted