[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: SAX LexicalHandler::comment issue
> What are other peoples thoughts? Is it worth proposing > startComment()/comment()/endComment() for SAX x.x? I tend to think not; what's the real win to changing that API? There's a measurable cost to changing APIs that are widely deployed ... I can't see an offsetting benefit. I'd rather discourage folk from using comments in applications, actually ... :) So far as I know, the primary use case for reporting comments is to support DOM bells'n'whistles. And W3C is, finally, looking at ways to disable such noise there. There's a similar issue with reporting PIs ... the data passed to the target can be arbitrarily large. Any application that really cares about the content of comments should really be using PIs instead. (Text editors aside -- and those can't really be using "Application" programming interfaces.) On the other hand, I can't see worrying that names for elements, attributes, entities, and notations have no size limits, which is the other main place that SAX expects data to be string-ized. - Dave
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|