Thanks for the clarification.
Simon
Joseph Kesselman wrote:
Perhaps this isn't the cleanest way of doing this from an OO point ofview, but it gets the job done.
The real glitch here is that CharacterDataImpl's name is misleading; it should probably have been called something like NodeCarryingTextImpl. If you want to blame someone for that, it's probably my fault.
But CharacterDataImpl is strictly an implementation detail; nobody but a Xerces implementer should ever have to be particularly aware of it. So this should, at worst, be a minor documentation nuisance.
Theoretically, we could rename it and nobody's code ought to break... but I'd want to poll the user community before we considered that; some folks have done weird things with internal classes in the past, and we'd need to balance the impact on them vs. long-term code clarity.
______________________________________ 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
