Re: Re: [xml-dev] ues-attributes2/entity-resolver2/locator2 read-only?

> Simialrly, some parsers may wish to allow the user to specify whether 
> Locator2 or Locator objects are passed. Ditto for Attributes2 or 
> Attributes objects. Certainly not all parsers would want to allow 
> this. Read-only should be an option for all three. The question is 
> whether write ever makes sense. I'm not sure.

Well, I can't see anything that write would do, that is necessary.
Do you need to tell the parser to pass Locator instead of Locator2?
I would think it is just as easy to *not* use the extra features
of Locator2, no matter what type of instance you get passed.

Yes, one might save the parser a few bytes of memory and possibly
a few CPU cycles by telling it: "I don't need Locator2".
But that would not amount to a measurable advantage, IMO.

Ditto for Attributes2.

Karl


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
List: sax-devel, [email protected]
See:  http://www.saxproject.org/
https://lists.sourceforge.net/lists/listinfo/sax-devel