Lists Home |
Date Index |
- From: David Brownell <firstname.lastname@example.org>
- To: email@example.com
- Date: Thu, 18 Nov 1999 09:57:19 -0800
Tim Bray wrote:
> The performance is good enough that in Lark, the limiting factor was
> my lousy input buffering, not the character class checking; and Lark
> was always in the top half of the performance table. -Tim
I think that's pretty typical. I've profiled several parsers by now,
and character class checking hasn't been a major issue ... usually
one or two percentage points CPU time for testing whether a character
works in a name (first/rest) or not.
The technique I used in Sun's parser may be good for many folk to steal.
It involves using the standard Character.getType() method (which has
access to lots of Unicode tables, and in recent JVMs uses native code
to quickly access them) and then filtering that output by the rules in
the XML spec.
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)