Xerces is a spaghetti code of intermixed and overlapping "dependencies"...
It seems that c++ coders don't care about modularity, everything calls everything else. I did a "port" of Xerces, to sas/c on os/390 and had to link statically, because sas/c does not have a good DLL architecture, and I discovered to my utter horror, that the sample apps when linked statically where 14 meg. If you use Xerces everything gets sucked in..... (of course this was long time ago 1.7) -----Original Message----- From: Purdy, Edgar M [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 10:00 AM To: [EMAIL PROTECTED] Subject: Header files I have implemented at DOM parser in c++ I have included the .dll and .lib files created when I compiled the Xerces package. By the time I was done trying to compile my application I found that I needed to include 135 Xerces specific .h / .hpp files. This cant be correct. Has anyone got an idea about how to pare down this list of include files. Ed Purdy --------------------------------------------------------------------- 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]
