It was clearly always a goal (though maybe not a first order one) that people would be able to write their own fully functional parsers. Why doesn't SAXParser itself need these things?
-------------------------- Dean Roddey The Charmed Quark Controller Charmed Quark Software [EMAIL PROTECTED] http://www.charmedquark.com "If it don't have a control port, don't buy it!" ----- Original Message ----- From: "Robert Buck" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, May 14, 2002 1:42 PM Subject: Re: Xerces C++ Exceptions not Exported > Yup, Dean is correct. I guess what I am looking for is a solution to my > problem that would enable me to *not* maintain a modified version of Xerces > in the MATLAB source tree. > > This is my ideal resolution: > > (a) export those two exception classes. > (b) add an accessor method on the sax2 parser impl to get at the scanner > (c) add an accessor method on the scanner to get to the grammar resolver. > > If (a) were done, I could create my own parser and scanner classes, so that > I can get at all the needed schema information. > If (b) and (c) were done too, I would not need to create my own parser and > scanner classes. > > What are peoples thoughts on incorporating these three changes to Xerces > versus just the first? Are there any objections to any of these changes? > > I am about to test my presumption, but I think if (a) were done I could > just create copies of the scanner and parser classes and modify them for > our own use, and avoid having to put Xerces under internal source control. > Of course if (b) and (c) were done too, that would mean much less work for > me as well. > > Bob Buck > > At 01:27 PM 5/14/2002 -0700, Dean Roddey wrote: > >Unix exports everything, which is something I think is a bad thing. But, it > >means you never fail to have something in a library, even if you weren't > >intended to have that access. In Windows it must be explicitly exported, > >else its considered an internal detail. > > > >From: "Jason E. Stewart" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Tuesday, May 14, 2002 12:53 PM > >Subject: Re: Xerces C++ Exceptions not Exported > > > > > > > "Robert Buck" <[EMAIL PROTECTED]> writes: > > > > > > > Using Visual Studio I link my application against Xerces and ICU. If > > > > I use either of those specific classes in my code I get unresolved > > > > link errors. The other exception types are exported in the API's and > > > > I have no problem with those. In fact, when I check the xerces dlls > > > > with a depends tool, neither of these two classes are exported. The > > > > header file confirms this. > > > > > > This is a windows-specific issue then. It works perfectly under > > > Unix. > > > > > > I'll let Tinny or someone else with windows knowledge help. > > > jas. > > > > --------------------------------------------------------------------- > 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]
