On Tue, 19 Oct 2004 10:15:06 +0100, Gareth Reakes
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> this is expected behavior. The rational is that recycling the
> pointer/memory is expensive in comparison to the likelihood of it being
> required.
That explains it. I've got a program where I'm accessing
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-45
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-50
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-90
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-150
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-171
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-178
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-179
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-194
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-197
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-224
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-239
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-253
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-254
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-259
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-291
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-292
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-299
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-301
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-312
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-313
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-355
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-371
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-378
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-397
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: PeiYong Zhang
Created: Tue, 19 Oct 2004 9:58 AM
Body:
Vladimir,
As the community becomes more and more concerned about the
license and copyright issues related to code contribution,
we would be more th
The following comment has been added to this issue:
Author: PeiYong Zhang
Created: Tue, 19 Oct 2004 9:56 AM
Body:
Valerio,
As the community becomes more and more concerned about the license and copyright
issues related to code contribution, we would be more than happy to check
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-416
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-424
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-452
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-465
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-494
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-640
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-650
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-688
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: PeiYong Zhang
Date: Tue, 19 Oct 2004 8:59 AM
BinInputStream derives from XMomory and when it gets deleted, the allocator is
retrieved and used to deallcate memory.
--
Message:
The following issue has been closed.
Resolver: PeiYong Zhang
Date: Tue, 19 Oct 2004 8:51 AM
using SAX may solve this problem since DOM is known memory thirsty..
-
View the issue:
http://issues.apache.org/
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-748
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-831
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-979
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: PeiYong Zhang
Date: Tue, 19 Oct 2004 8:32 AM
Private ctor/dtor is meant for Singleton.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1075
H
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1193
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1237
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1247
Here is an overview of the issue:
-
That's strange, as the failure is occurring when trying to execute a.out.
It looks like your LD_LIBRARY_PATH doesn't contain /usr/local/lib; can you
check?
Alberto
At 10.40 19/10/2004 -0400, Dorn Hetzel wrote:
On a vanilla RH9 box with gcc 3.2.2,
I'm trying to build xerces-c against libwww, usin
On a vanilla RH9 box with gcc 3.2.2,
I'm trying to build xerces-c against libwww, using
xerces-c-current.tar.gz which contains xerces-c-src_2_5_0
and using w3c-libwww-5.4.0.tgz which is configured as
follows:
in /usr/local/src/w3c-libwww-5.4.0/
./configure --with-expat '--with-ssl=-L/usr/local/
Hi,
this is expected behavior. The rational is that recycling the
pointer/memory is expensive in comparison to the likelihood of it being
required.
Gareth
Hua-Ying Ling wrote:
Hi,
I find that if I run the code below in a tight loop, the memory
footprint will keep growing unless I call docume
Hi,
I think the easiest way would be to do as you describe - create the
string from the SAX events.
Gareth
Xiaofan Zhou wrote:
Hi All,
I have a need to do the following:
Suppose I have an element A that has a sub structures (e.g it has
child elements which could again have child elements
Hi,
http://www.w3schools.com/xml/default.asp
or look at the specs on www.w3.org. If you want more tutorials type "xml
tutorial" into google.
Gareth
Samuel Tonini wrote:
hi All
Im starting with XML and C++ programming, but now i have a lot of problems. Im a rookie-developer, but im want to unde
The following issue has been updated:
Updater: Michael McMaster (mailto:[EMAIL PROTECTED])
Date: Tue, 19 Oct 2004 1:28 AM
Comment:
Solution.
Changes:
Attachment changed to DOMString.patch
-
For
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/XERCESC-1291
Here is an overview of the issue:
-
51 matches
Mail list logo