Message Loaders

Hi, all Xerces-C++ supports a number of message loaders ICU Message Loader use ICU resource bundle to load locale-specific message work for most Windows and Unix/Linux platforms Message Catalog Message Loader use system message cata

Re: sample code?

Hello Sarah, can you tell us exactly what you're trying to do, what you need Xerces to do for you? Xerces is quite a beast [I hope the contributors don't mind me saying that] and coming to it fresh I can certainly see how you might find it a daunting prospect – I did. But nevertheless, regardless

sample code?

To all, I am still kind of lost on using Xerces for parsing. Does anyone have any extra documentation or sample kind they can send my way? I've ordered the book that was recommended to me by someone (Erick?) but it hasn't arrived yet. I really think that the documentation and sample code needs to

Re: Unit Testing, Test Suite

"Gareth Reakes" <[EMAIL PROTECTED]> writes: > Id definitely be interested in that. At the very least I would like > to run the tests as part of the checking the nightly build for > linux. There are some tests under the tests directory (the DOM > tests in particlar test some of the API) but more i

DO NOT REPLY [Bug 15372] New: - DOMBuilder::parseFromURI ignores result of handleErrors

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 15371] New: - Requesting schema validation by DOMBuilder is non-obvious

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: FW: Const-correctness in Xerces and TreeWalker

* Erik Rydgren <[EMAIL PROTECTED]> [2002-12-13 17:07]: > The performance hit comes from larger vtables that needs to be set at object > creation. After that... And I think there should not even be a larger vtable. Ideally, to avoid inconsistencies between the const and non-const variants, the impl

RE: FW: Const-correctness in Xerces and TreeWalker

Hi, I think it must have been me who has been unclear :). I am not asking the type to enforce its own constness. If you want a const iterator then you ask for one from the Document. This returns a completely different class with const methods that return const DOMNodes and it has (in the ca

RE: FW: Const-correctness in Xerces and TreeWalker

> Hi, > > On Fri, 13 Dec 2002, Brad Settlemyer wrote: > > > No, that seems like a bad idea as const is used for compile time const > > checking by the compiler, but when implemented as a class the ability to > > substitute const instances is different I think. (e.g. const ness can > > always be re

Re: FW: Const-correctness in Xerces and TreeWalker

* Tinny Ng <[EMAIL PROTECTED]> [2002-12-13 16:35]: > I think we need to think again about this, as it's not only > "createTreeWalker", the DOM document has all those create methods like > "createElement", "createAtttribute" ..., and then all those inherited > DOMNode interface like "removeChild

RE: FW: Const-correctness in Xerces and TreeWalker

The vtables is a overall hit for the class definition not the object itself. This memory is rather minuscule compared to the memory DOM nodes take. Maybe we should try to optimize the memory each DOM node takes where we can get better performance gains. Kiran -Original Message- From: Erik

RE: FW: Const-correctness in Xerces and TreeWalker

After closer thought... The vtable is created at compiletime and is shared between every instance of a class. Hence the only performance difference between 10 or 1 virtual methods is only the below mentioned cache miss. / Erik -Original Message- From: Erik Rydgren [mailto:[EMAIL PROTE

RE: FW: Const-correctness in Xerces and TreeWalker

Hi, > Just my 2 cents... > > Why not make the compiler worry about the overloading? > Create 2 methods in DOMNode: > > DOMDocument* DOMNode::getOwnerDocument(); > const DOMDocument* DOMNode::getOwnerDocument() const; > > Which handles the getownerdoc problem. Then implement 2 methods in > DOMD

RE: FW: Const-correctness in Xerces and TreeWalker

Yepp it is a tedius work. But I disagree that you will have to duplicate ALL functions. Either the method does not change the object: getAttribute, getTagname. (implies const methods) or it does change the object: insert, delete, setAttribute and so on (non-const method) However functions that retu

RE: FW: Const-correctness in Xerces and TreeWalker

Hi, On Fri, 13 Dec 2002, Brad Settlemyer wrote: > No, that seems like a bad idea as const is used for compile time const > checking by the compiler, but when implemented as a class the ability to > substitute const instances is different I think. (e.g. const ness can > always be resolved at comp

RE: FW: Const-correctness in Xerces and TreeWalker

No, performance would be the same at worst and possibly be improved by overloading on const-ness. Const is evaluated solely at compile time -- even const casts are only evaluated at compile time. Const functions can theoretically be much faster than their non const bretheren as the compiler knows

Re: FW: Const-correctness in Xerces and TreeWalker

I think we need to think again about this, as it's not only "createTreeWalker", the DOM document has all those create methods like "createElement", "createAtttribute" ..., and then all those inherited DOMNode interface like "removeChild", "replaceChild" ...etc. If we have to overload each and

DO NOT REPLY [Bug 6407] - Multiple ampersands not interpreted correctly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

RE: FW: Const-correctness in Xerces and TreeWalker

Thanks, I became a bit worried there and I just HAD to check myself. And it works, of course ( No false modesty here :) ) But you beat me to it. / Erik -Original Message- From: Ingolf Steinbach [mailto:[EMAIL PROTECTED]] Sent: den 13 december 2002 16:01 To: [EMAIL PROTECTED] Subject: Re:

Re: FW: Const-correctness in Xerces and TreeWalker

* Jennifer Schachter <[EMAIL PROTECTED]> [2002-12-13 15:55]: > This wouldn't help our problem: You cannot overload based on return > type... [...] > On Fri, 13 Dec 2002, Erik Rydgren wrote: [...] > > DOMDocument* DOMNode::getOwnerDocument(); > > const DOMDocument* DOMNode::getOwnerDocument() const

RE: FW: Const-correctness in Xerces and TreeWalker

This wouldn't help our problem: You cannot overload based on return type... Cheers, Jenn On Fri, 13 Dec 2002, Erik Rydgren wrote: > Just my 2 cents... > > Why not make the compiler worry about the overloading? > Create 2 methods in DOMNode: > > DOMDocument* DOMNode::getOwnerDocument(); > co

RE: FW: Const-correctness in Xerces and TreeWalker

Just my 2 cents... Why not make the compiler worry about the overloading? Create 2 methods in DOMNode: DOMDocument* DOMNode::getOwnerDocument(); const DOMDocument* DOMNode::getOwnerDocument() const; Which handles the getownerdoc problem. Then implement 2 methods in DOMDocument. DOMTreeWalker* D

RE: FW: Const-correctness in Xerces and TreeWalker

No, that seems like a bad idea as const is used for compile time const checking by the compiler, but when implemented as a class the ability to substitute const instances is different I think. (e.g. const ness can always be resolved at compile time, type cannot). I can't see any advantage in impl

RE: FW: Const-correctness in Xerces and TreeWalker

Hi all, I came across a problem related to this and would like to know how other people handle this/ what they think. We need to create a DOMTreeWalker from a const node. Now we do DOMDocument *doc = node->getOwnerDocument(); this is already weird as we get back a non const and could trav

Re: Unit Testing, Test Suite

Hi Jason, Id definitely be interested in that. At the very least I would like to run the tests as part of the checking the nightly build for linux. There are some tests under the tests directory (the DOM tests in particlar test some of the API) but more is better! Gareth On 12 Dec 20

DO NOT REPLY [Bug 5854] - Patches and .spec file for rpm creation of 2.2.0

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

DO NOT REPLY [Bug 5854] - Patches and .spec file for rpm creation of 1.6.0

gzilla/show_bug.cgi?id=5854 Patches and .spec file for rpm creation of 1.6.0 --- Additional Comments From [EMAIL PROTECTED] 2002-12-13 08:35 --- Created an attachment (id=4159) Latest proposed spec file for Xerces-C++ RPM (CVS 20021213 + p

DO NOT REPLY [Bug 5854] - Patches and .spec file for rpm creation of 1.6.0

gzilla/show_bug.cgi?id=5854 Patches and .spec file for rpm creation of 1.6.0 --- Additional Comments From [EMAIL PROTECTED] 2002-12-13 08:34 --- Created an attachment (id=4158) Patch to fix bugs in xerces-c.spec (in CVS on 20