> At 10:12 AM 13/04/98 -0400, David Megginson wrote:
> >The first, "getAttributeListLength", is the ugliest. It is simple to
> >avoid this problem by creating a separate class for SAXAttributeList,
> >rather than implementing it in the main driver -- what does everyone
> >else think about this question?
>
> Well, yes. But I thought you were dead set against having any
> extra classes? -Tim
If I'd stuck with this, there would still be only two interfaces in
SAX: the parser and the handler.
What I'm talking about here, though, is an extra class in a specific
parser's implementation. Most SAX parsers will implement SAXParser,
SAXAttributeList, and SAXLocator with the same class; they are free,
however, to use a separate class for each if method-name collisions
become a problem.
All the best,
David
--
David Megginson ak117@freenet.carleton.ca
Microstar Software Ltd. dmeggins@microstar.com
http://home.sprynet.com/sprynet/dmeggins/
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)