Re: DOMInputSource vs InputSource (was Re: Memory Leak?)

"Jason E. Stewart" wrote:
> 
> Brian Faull <[email protected]> writes:
> 
> > Trying to implement the solution you list -- but I need to take
> > input from a local variable. My previous attempt used a
> > XercesDOMParser rather than DOMBuilder... and XercesDOMParser::parse
> > was AbstractDOMParser::parse, which took an InputSource (can be
> > StdIn*, MemBuf*, LocalFile*, ...).  DOMBuilder::parse rather takes a
> > DOMInputSource, which seems that it may only be a file or URL
> > natively.
> >
> > There is a handy class called Wrapper4InputSource which isa
> > DOMInputSource which can allow an InputSource to be used as a
> > DOMInputSource. However...  Wrapper4InputSource doesn't appear to be
> > available in XML::Xerces. I didn't see any tests with a
> > DOMInputSource used, either... Have I missed something, or...?
> 
> Aha! I wondered what that class was for (blush) ...

So did I. It was mind-numbing looking at the API docs for DOMInputSource,
InputSource, and Wrapper4* classes for both... :-\ I'm no OO expert,
but... hmmm...

> The file Xerces.i controls which Xerces-C API classes that I
> wrap. Currently, this is done manually - I just update the file an a
> per-need basis. So if a class' header file is not there, XML-Xerces
> won't know anything about it.
> 
> I was just thinking that it would be convenient to know what public
> header files are available and which ones I'm not currently wrapping.

Good to know, and great idea -- I'll view that file in the future.

> I'll add it and commit it to the SVN repository. You can either grab
> it from there or I can make a dev snapshot tarball.

Installed and like svn, but don't seem to have the right configuration yet
-- can't snarf the repository. If you would post a tarball at your
convenience, that would be super. 

Thanks a bunch!
-brian


> Cheers,
> jas.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]