Joseph Kesselman wrote:
There might be more if XNI made doing so easier. Last time I tried doing
this -- admittedly a long time ago -- I had to wrestle with it for a while
Like I said in my response to Arnaud, it's hard for
me to relate since I worked on the design. But I do
see how hard it would be for people to use Xerces
parser configurations as examples because of the
complexity of a complete parser. And that's why I
spent so much time on the XNI Manual in the docs.
But if that's not sufficient for people, then we
should probably add more material.
If anyone is interested in making parser configs
using the framework, it may be easier to start with
a simpler example like NekoHTML. I originally wrote
it as an XNI example (which just happened to be
useful in its own right). It doesn't re-use any
internal Xerces components and has an extremely
simple pipeline setup. So that might be an easier
path for people to come up to speed.
> and never did really find a way to structure it as I wanted (as a
> hierarchical architecture, with a set of components being concatenated to
> form a higher-level component).
Way back when, Ted Leung and I talked about making
a parser configuration that would read an XML-based
description of a parser and it build it dynamically.
But we never got around to writing it. I wonder if
such a beast would be useful to people...
--
Andy Clark * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
