Just being anal but:
char *sp = s.transcode();
std::cout << sp;
delete sp;
std::cout << "transcode() string deleted\n";
return 0;
is in error. It should be "delete [] sp" or you will get undefined results.
--
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PR
, 2001 11:32 PM
Subject: RE: Problem deleting transcoded data
> I gather the app uses all static libraries except for xerces.
> On Solaris this should not be a problem as the following code
> demonstrates:
> /* transcode_test.cpp */
> #include
> #include
xerces-c1_4.so
$ a.out
Some text!
transcode() string deleted
Zartaj
-Original Message-
From: Mitchell, Raymond [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 31, 2001 10:51 AM
To: '[EMAIL PROTECTED]'
Subject: Problem deleting transcoded data
The project I am working on makes use of
Ray,
I use Xerces-C on Solaris, HPUX, and AIX, and have had no problems with
the memory. I'm currently using Xerces 1.3.1, because that's the API our
code was written against. Since it looks like 1.5 will soon be out, I will
have
to look at moving to 1.4 - I don't like bleading edge stuff - I pre
y, May 31, 2001 1:51 PM
> To: '[EMAIL PROTECTED]'
> Subject: Problem deleting transcoded data
>
> The project I am working on makes use of Xerces-C on Win2000, Solaris, and
> Mac. I have run into a problem on Windows and Solaris. When I attempt to
> delete the memo
tware
[EMAIL PROTECTED]
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
- Original Message -
From: "Mitchell, Raymond" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 31, 2001 10:50 AM
The project I am working on makes use of Xerces-C on Win2000, Solaris, and
Mac. I have run into a problem on Windows and Solaris. When I attempt to
delete the memory allocated during a transcode, I get an illegal memory
access.
On Win2000, my project makes use of the Multithreaded runtime libra
