"Brendan Reville" <[EMAIL PROTECTED]> writes: > > You may need to define what you mean by "standalone SAX parser." > > We have an > > app that statically links Xerces and uses the SAX parser. (Mind you, it's > > based on a very old version of Xerces.) Is that what you mean? > > The ultimate goal is to avoid a half-meg overhead in application size, when > all I need is the very simple ability to SAX parse a file. > > Going by Dean's comments, I'm guessing that the statically linked app has a > fairly large executable on disk, because all the DOM stuff ends up in there > too?
I haven't looked into this, but apparently Xerces-J now has three jar files, one for SAX, one for DOM, and one for common. I believe this ability would be very nice to have in Xerces-C, not only because of memory footprint, but also because of application startup time. The Perl Module, XML:Xerces, that wraps Xerces-C could then be split into three pieces, and script writers would get faster, smaller applications. jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
