Ok, I should have been more explicit, as usual. It doesn't use anything in
std::, or at least it hasn't traditionally. That might have started
happening lately, and some of the platform drivers might, since they can do
what they want and they know what they can expect on that platform. Anyway,
the parser generally just used the least language, runtime, and OS services
it could get away with and still meet its requirements and be robust, for
portability reasons.

--------------------------
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: "Miroslaw Dobrzanski-Neumann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, January 20, 2002 11:07 PM
Subject: Re: Core Dump after instantiating a DOM_Node


> std::exception is part of the language not STL
>
> On Fri, Jan 18, 2002 at 05:33:11PM -0800, Dean Roddey wrote:
> > The parser traditionally did not assume the existence of, or use, the
STL
> > stuff, so that it could be used in systems in which that was not
practical,
> > e.g. some kinds of embedded systems perhaps. And, it was to avoid
> > portability issues with STL, because the parser covers a lot of
territory.
> > It really only uses the most primative of language runtime services, or
it
> > used to. That may have changed since I moved on.
> >
> > >
> > > Just out of curiosity, why is it that the set of *Exception classes in
the
> > > xerces toolkit do not inherit from std::exception?
> --
> Miroslaw Dobrzanski-Neumann
>
> MOSAIC SOFTWARE AG
> Base Development and Research
> Tel +49-2225-882-291
> Fax +49-2225-882-201
> 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]

Reply via email to