I think that the main problem that's come up is that SAX2 stuff is now being used in the core scanner. So you can't get rid of SAX/SAX2 at all anymore. You can probably still get rid of the DOM ok, AFAIK. But its still kind of a manual operation to get rid of anything, whereas it used to be all maintained cleanly.
Actually, the SAX thing is more than just a 'get rid of it' problem. It a circular dependency, so you can't even build it as separate DLLs, because SAX needs the core stuff, and the core stuff now needs the SAX stuff. So its just a bad layering issue, separate from whether you want to dump parts of it or not. ------------------------------------- Dean Roddey The Charmed Quark Controller [EMAIL PROTECTED] www.charmedquark.com -----Original Message----- From: Shah Amit-ASHAH3 [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 12:31 PM To: '[EMAIL PROTECTED]' Subject: RE: Standalone SAX parser? Hello, If I understand this issue right .. Brendan wants to get rid of the DOM part .. if this is so .. it is possible, I am using v1.4 and I dont include DOM, COM and SAX2 directories in my builds at all .. and there seems to be no problem .. I compile all the others, link and generate one .out file .. I hope that helps .. ~amit -----Original Message----- From: Jesse Pelton [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 3:00 PM To: [EMAIL PROTECTED] Subject: RE: Standalone SAX parser? As it happens, our app uses SAX to parse documents and DOM to construct them, so we pull in pretty much everything. In theory, if we didn't use the DOM stuff, the linker would omit it. Even if this is the case, this approach makes less efficient use of system resources than a DLL, because other apps on the machine that use Xerces will have their own copy of the same code. I don't know whether Dean's original design goal of separately buildable subsystems could be met by revisiting the current code. That goal seems to have dropped by the wayside some time ago, and dependencies have crept in that may be difficult to break. I doubt the core development team is going to take this on, because this doesn't seem to be an issue for most Xerces users. It makes a difference to you, so you've got more motivation than most to address the issue. Consider exploring the issues, posting your thoughts (discussion of the problem and/or possible solutions), and creating a patch on your own or with the cooperation of like-minded individuals. -----Original Message----- From: Brendan Reville [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 28, 2002 3:14 PM To: [EMAIL PROTECTED] Subject: RE: Standalone SAX parser? > 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] --------------------------------------------------------------------- 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]
