... I tend to agree. Within a specific body of code, one can certainly know
and assert that all Booleans will be the canonical TRUE and FALSE instances
and leverage that for improved performance. But an abstract API probably
shouldn't make that assumption; even if you document it to death, you're
setting yourself up for an endless FAQ stream when people forget this
detail.
I also submit that setParameter is a comparitively infrequently used
operation, and micro-optimizing it at the cost of clarity/robustness is
inappropriate.
If the DOM WG really insists on doing it anyway, the specific TRUE and
FALSE objects for this use should probably be supplied by the API they will
be passed to rather than by the Boolean class, to make the idiom portable
across implementations and particularly across languages.
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
