SAX: External Entity Start and End (question 2 of 10)

[Paul Prescod]

David Megginson wrote:
> 
> The only way that I can resolve this correctly is if I know the URI of
> the current external entity.  In Lark, you provide this information
> with a separate Entity argument to each callback; this is a legitimate
> (and more powerful) option, but from the perspective of SAX, it ends
> up complicating the entire API instead of just adding two
> easily-ignored callbacks.

It is possible to have "invisible arguments" to a callback that do not
complicate the interface. This sounds very mysterious, but an "invisible
argument" is just a variable whose value can be fetched through a parser
method. getCurrentEntity() or getFileEncoding() would be examples.

I think that this is the right way to handle this entity problem.
Require the parser to track the information rather than the application.

 Paul Prescod
--
http://itrc.uwaterloo.ca/~papresco

Art is always at peril in universities, where there are so many people, 
young and old, who love art less than argument, and dote upon a text 
that provides the nutritious pemmican on which scholars love to chew. 
				-- Robertson Davies in "The Cunning Man"



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)