[ http://issues.apache.org/jira/browse/XERCESC-1294?page=comments#action_54862 ]
PeiYong Zhang commented on XERCESC-1294:
Norman,
Can you post the list of offending methods? thanks.
Rgds,
PeiYong
> Compiler Warnings on IRIX with MIPSpro co
[ http://issues.apache.org/jira/browse/XERCESC-1292?page=comments#action_54861 ]
PeiYong Zhang commented on XERCESC-1292:
Ralf,
I've tested this (SAX2Count) with XercesC2_6_0, and the noOfAttrs is 1 (not 2, and
the default='0' is in the xsd
> Afaik, when overloading 'placement' new and delete
> like that, the only time the corresponding overload
> of delete will be called is if the constructor throws.
> All other times you have to call the destructor and
> the right version of delete yourself.
This is not true. If a class implements
On Sun, Oct 31, 2004 at 10:18:54AM -0800, [EMAIL PROTECTED]
wrote:
> > > All classes that derive from XMemory use "placement" new with a
> > > MemoryManager instance, and the normal delete expression. The
> > > call
> stack
> > > you posted looks fine.
> >
> > But is this the correct behaviour
Hi Graham,
> > All classes that derive from XMemory use "placement" new with a
> > MemoryManager instance, and the normal delete expression. The call
stack
> > you posted looks fine.
>
> But is this the correct behaviour? I think the destructor for the
> object should be called, then the op
On Sat, Oct 30, 2004 at 09:20:46PM -0400, [EMAIL PROTECTED] wrote:
> > I'm seeing a crash when an IGXMLScanner held statically is destroyed.
> > I'm using Xerces 2.3.0 on linux compiled with gcc 3.2.
>
> Can you elaborate on what you mean by "held statically?" You shouldn't
> have any static ins
Sorry for posting this so many times. I sent this email several
days ago, and when it didn't show up on the list right away, I
re-sent it several times over.
My apologies,
Matt
On Tue, Oct 26, 2004 at 01:05:27PM -0700, Matt Garman wrote:
> I'm trying to link in a static xerces library on Win32
