t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 28, 2001 10:24 PM
Subject: RE: asserts in Xerces
> But then apparently, the Xerces 1.4 lib is not a production build ?
>
> Ivan
>
> -Original Message-
> From: Andy Heninger [mailto:[EMAIL PROTECTED]]
But then apparently, the Xerces 1.4 lib is not a production build ?
Ivan
-Original Message-
From: Andy Heninger [mailto:[EMAIL PROTECTED]]
Sent: 29. mars 2001 05:23
To: [EMAIL PROTECTED]
Subject: Re: asserts in Xerces
I put many of those asserts in there.
Some of them are checking
uot;Dean Roddey" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 27, 2001 10:48 PM
Subject: Re: asserts in Xerces
> I think that it was always agreed that those asserts should be dealt
with,
> since that's not the way the rest of the system works. I
tware
[EMAIL PROTECTED]
http://www.charmedquark.com
"I'm not sure how I feel about ambivalence"
- Original Message -
From: "Uthus Ivan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 27, 2001 10:41 PM
Subject: RE: asserts in Xerces
>
Aren't there anyone who would like to comment on this issue ? What are the
thoughts on asserts vs exceptions in Xerces for example ?
Ivan
-Original Message-
From: Uthus Ivan [mailto:[EMAIL PROTECTED]]
Sent: 26. mars 2001 10:54
To: '[EMAIL PROTECTED]'
Subject: asserts
Hi!
We have had some problems in our production environment with the (prebuilt)
Xerces lib version 1.4 for AIX 4.2. On some large (5.4 MB) files, the lib
asserts at this location in NodeVector.cpp:
void NodeVector::init(unsigned int size) {
assert(size > 0);
data = new NodeImpl *
