"Steven N. Hirsch" <[EMAIL PROTECTED]> writes:

> On 16 Mar 2002, Jason E. Stewart wrote:
> 
> > You're welcome. Thanks for letting us know. I do a lot of work for
> > this project, and it's completely voluntary. I haven't had a lot of
> > time to devote to the project lately, and I've felt a bit guilty. 
> > 
> > But at the same time, I haven't heard a lot of feedback recently, and
> > so I begin to wonder whether I'm developing an XML parser just for
> > myself. 
> 
> Not at all!  I've been quite happy with Xerces-perl and haven't had a 
> compelling reason to post anything in a while.  

Good! Glad to hear it.

It's funny but it seems that the only way a maintainer can know how
popular a project is is by how many people complain about something
not working. Not exactly optimal feedback - it encourages me to make a
'broken' release every now and then just to see who notices ;-)

> That said, I am curious about your recommendations for handling
> 'xlink' constructs.  In my naivety, I thought that the parser would
> either resolve these and include them or have a switch to effect
> that behavior.  Since that turns out not to be the case, I'd
> appreciate some input on how to accomplish this through the IDOM
> interface, i.e. have the parsed model available with the xlinked
> element replaced by the target document.

That's a big project. What I would do is to not touch the core IDOM,
but to parse the document as-is, then pass the IDOM_Document instance
off to a custom library method that you write to handle XLink'ed
nodes. It would traverse the tree, and replace the XLink nodes with
the ones being referered to.

To me it's simpler to do it in Perl. Otherwise, you'll have to
implement it in C++, and create some subclass of IDOMParser, like
IDOMParser-XLink, that does it for you automatically.

> I keep bashing away at the AIX exception-handling issues as time
> permits, but have gotten exactly nowhere with it :-(.  It's tough to
> debug something when the debugger either dumps core itself or
> refuses to load the executable.

Hmmm. I wish I had some valuable information, but I don't.

jas.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to