Given two values a and b, it's a.constructor.prototype and
b.constructor.prototype that need to be compared, not a.prototype and
b.prototype (both undefined, and therefore always equal). Perhaps the
spec should be clear about this.
2) Another issue I've encountered is with assert.throws(). Rhino pukes
out because "throws" is a reserved keyword. I had to revert to
assert.error() instead.
These are both bugs, in my opinion, and should be fixed in the next rev.
Kris Kowal
I've proposed a rev 1.0.1 for Unit Testing. These are the differences:
The only contentious point is that I've changed "throws" to "error". I
don't think this implies that "throws" should be removed from all
implementations, just that it's deprecated. Basically, implementations
can claim to be both 1.0 and 1.0.1 compliant by supporting both.
Kris Kowal
Kris Kowal
--
You received this message because you are subscribed to the Google Groups "CommonJS" group.
To post to this group, send email to comm...@googlegroups.com.
To unsubscribe from this group, send email to commonjs+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/commonjs?hl=en.
Ates and I appear to both instinctively use "error". I don't think
"raises" is significantly better, since the verb/noun in JavaScript is
throw/error, not raise or handle exception. At the very least, it's
not worth the effort to revise the proposal.
Kris Kowal
2) Another issue I've encountered is with assert.throws(). Rhino pukes
out because "throws" is a reserved keyword. I had to revert to
assert.error() instead.