Lists Home |
Date Index |
- From: Lars Marius Garshol <email@example.com>
- To: <firstname.lastname@example.org>
- Date: 27 Mar 1999 21:32:24 +0200
* Lars Marius Garshol
| I'm a bit unsure why you think the unique method is needed,
| though. What kinds of uses do you have in mind for it?
* Bill la Forge
| From previous discussion on this list, I gathered that many parsers
| did the equivalent of String.intern(), but avoided the JavaSoft
| implementation for extra speed. If this is the case, then a filter
| needs to use the parser's own intern function to preprocess its
| constants before testing for matches in the startElement events.
Ah, I thinking didn't think of that. Now that I've had some more time
to think about this I realize that this would also be useful for
filters that create new names, such as XAF.
| So the short answer is yes, intern is beter than unique. I should
| have checked the lang package first.
This terminology is also used in Common Lisp and Python, and probably
many other places as well.
| My interest here is, instead, to define a means for sharing the
| element stack across independently developed filters. Just about
| every filter which does anything interesting ends up implementing
| its own element stack. Why not have one filter that does that, and
| let the rest get it from their "parser".
Another good point, and a very good idea, too.
However, then we need to define the element stack interface and what
should be included there. Just the elements? Elements and attributes?
Elements, attributes and sibling number? Which entity each element
Maybe this should be done outside the SAX core? On the other hand, if
filters are included I think this should be too.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)