DO NOT REPLY [Bug 4655] - config.status be included in all future binary releases

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 4873] - ICU 2.0 breaks Xerces 1.5.2 build

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: Plan for Xerces-C++ 1.6

Michael, Just checked the mail archive, and I think you have submitted two patches. One on Sept 27, and one on Oct 1 To avoid grepping the wrong patch, can you zip all your patches (better use the latest code base) and resend the zip file again? Thanks!! BTW I notice your patch in IconvTra

RE: Deleting objects from the DOM

Thanks, but I guess I have a more specific question for your vague answer... Say I DOMParse and load an existing XML doc, then want to delete an Element, and any of it's associated child nodes, how would I do it? Do I simply find the node of type DOM_Element and assign it =0? Or must I assign 0

DO NOT REPLY [Bug 5045] New: - API Documentation webpage refers to v1.5.2

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: Plan for Xerces-C++ 1.6

Is it possible to integrate the FreeBSD support supplied by me some weeks ago? -- Michael Huedepohl, Mozquito Technologies Tinny Ng wrote: > > Hi all, > > We've finished most of the schema features, and are now in testing and > wrapping up mode. So I think it's time to call for Xerces-C++

RE: Deleting objects from the DOM

Memory allocated to a DOM document is released when the last handle (DOMDocument object) to the documentimplementation dies. If you need to alter the document tree then you want to use the DOM_Node::removeChild method. roObsoleteNode = 0; // Only closes the handle to the implementation of the o

Re: Deleting objects from the DOM

On Fri, 23 Nov 2001 11:57:55 +0200, Pat O'Neil wrote: > I have found no documentation that describes deleting a DOM_Node (and >possibly its children) from the heap. Have I missed reviewing a piece of >sample code, or should I try grabbing pointers and deleting them, or a third >more intell

Re: Storing character positions in DOM

On 22 Nov 2001 08:39:31 -0700, Jason E. Stewart wrote: >I'd actually like to see this get implemented for the SAXParser. I >don't need to know where the attributes are, just the elements, so SAX >would do all of what I need. You DO realize that the SAX Locator interface probably does what you wa

RE: Storing character positions in DOM

The solution for you is virtual methods. If you change all methods in the SAX parser to virtual then you can subclass the parser and override the functions in the original code to do what you want and still have the original functionality to back you up. The benifit is that you will have to modify

Deleting objects from the DOM

Hi, I have found no documentation that describes deleting a DOM_Node (and possibly its children) from the heap. Have I missed reviewing a piece of sample code, or should I try grabbing pointers and deleting them, or a third more intelligent alternative that I cannot fathom? Thanks Pat O'

Re: Storing character positions in DOM

From: "Jason E. Stewart" <[EMAIL PROTECTED]> > "Cyberthymia" <[EMAIL PROTECTED]> writes: > > > I'm currently in the process of adding an XML parser to a project > > I'm working on, using the DOM parser in XercesC. The problem I've > > got at the moment is that I need to be able to tie in the no