> I have a question about the DOMString class. I am writing a
> JNI-based library to access Xerces-J DOMs from C++. In looking for a
> decent string class to pass data around my wrapper classes, I came
> across Xerces-C's DOMString class.
Just out of curiosity why not use Xeces-C if you are
gt; Subject: RE: DOMString class
>
>
> Also, do any of these functions do something funky with threading?
> My library is in a delicate state as it has been loaded by Java's
> System.loadLibrary function.
>
--
Also, do any of these functions do something funky with threading?
My library is in a delicate state as it has been loaded by Java's
System.loadLibrary function.
>>I suspect you haven't called XMLPlatformUtils::Initialize.
>>
>Ahh, this is just what I was looking for. I assume I should just
>
>I suspect you haven't called XMLPlatformUtils::Initialize.
>
Ahh, this is just what I was looking for. I assume I should just
call that function once when my library is loaded? Are there any
destruction functions that need to be called when the library
terminates?
I have tried calling that
I suspect you haven't called XMLPlatformUtils::Initialize.
-Original Message-
From: Tobias McNulty [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 06, 2001 10:35 AM
To: [EMAIL PROTECTED]
Subject: RE: DOMString class
Doug,
I apologize, that was an error in my e-mail. It s
Doug,
I apologize, that was an error in my e-mail. It should have read:
DOMString* myStr = new DOMString("foo");
as you also stated in your e-mail. That is what the actual code I
was compiling looked like.
I do delete the pointer later on in my code, but that is not the
point. My library
Tobias,
In C++, the new operator returns a pointer to the newly created object. So
at first glance, your code should be modified to read:
DOMString* pMyStr = new DOMString("foo");
Later in your code, before pMyStr goes out of scope, you should call
delete pMyStr;
to release the memory explici
