Thanks for the reference, it does appear that the issue was settled in the DOM WG. I
would have personally leaned the other way, preferring to detect and throw an
exception when an expression has
resulted in a negative count instead of interpreting it as a platform-dependent large
number. I personally don't see the elimination of "unsigned" as a limitation of the
Java platform, but a
purposeful elimination of a dangerous behavior. I would lobby that you reconsider the
use of unsigned in future DOM interfaces.
It does mean that the tests that pass negative positions or counts (for example,
CharacterDataIndexSizeErrSubstringNegativeOffset,
CharacterDataIndexSizeErrSubstringCountNegative,
CharacterDataIndexSizeErrDeleteDataOffsetNegative,
CharacterDataIndexSizeErrDeleteDataCountNegative, have different expectations on
platforms that use unsigned values and should be written to reflect
that.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
