> 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? - Brendan > -----Original Message----- > From: Brendan Reville [mailto:[EMAIL PROTECTED]] > Sent: Thursday, May 23, 2002 2:47 PM > To: [EMAIL PROTECTED] > Subject: Standalone SAX parser? > > > > hi all, > > (I think I'll just ask this every 6 months to see if anything has > changed :) > > Has anybody managed to build a standalone SAX parser? > > I'm trying to avoid including a half-megabyte DLL with every > download of our > software. > > thanks > > - Brendan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
