Re: Changing include to include/xercesc

2001-08-15 Thread Murray Cumming
"Arnold, Curt" wrote: > > I haven't been following this thread and it troubles me that appears that it would >require touching every single include of a Xerces header file at least in >applications (and possibly in the Xerces > code base itself)? No, I have said several times that this will no

RE: Changing include to include/xercesc

2001-08-15 Thread Arnold, Curt
I haven't been following this thread and it troubles me that appears that it would require touching every single include of a Xerces header file at least in applications (and possibly in the Xerces code base itself)? And the problem seems pretty vague, at least to a (primarily) Windows develope

Re: Changing include to include/xercesc

2001-08-15 Thread Arnaud Le Hors
As far as I am concerned I don't have a pb with moving all the headers into a specific subdirectory but I must say I really don't like the name "xercesc". Why do we need a 'c' here? You're not concerned that it might conflict with xercesj headers are you? ;-) I suggest, if you change, to simply us

RE: DOM tree to a file

2001-08-15 Thread Aldrich, Tim
search the archives for DOMSerializer.cpp . HTH Timothy R Aldrich CREDIT | FIRST SUISSE | BOSTON Global Web Services (NYC) Voice: (212) 325-8652 Fax:(212) 325-9596 E-mail: mailto:[EMAIL PROTECTED] Pager: (877) 553-8722 -Original Message- F

Re: XercesLib and Borland C++Builder 5

2001-08-15 Thread Chris Hill
At 11:15 AM 8/15/2001, Don Mastrovito wrote: >Chris, > >Yes it can. I don't use that feature too often, having the IDE >available. In the IDE, select "Project|Export Makefile" from the >menu. I've pasted a copy of that makefile below. In a DOS box, set your >path to xerces-c-src1_5_1\Projec

limit on the buffer size for parsing?

2001-08-15 Thread Aniruddha Shevade
Hi Is there any limit on the buffer size which can be parsed by the xerces parser Thanks Aniruddha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: XercesLib and Borland C++Builder 5

2001-08-15 Thread Herb Chong
choosing Options on the .lib project and changing it to Release mode seems to corrupt the build enough to make only a small portion of the DLL. i'll have to do more experiments. Herb

char* XMLString::transcode(const XMLCh *const)

2001-08-15 Thread Paul Burlumi
Documentation for the method: char* XMLString::transcode(const XMLCh *const) found here: http://xml.apache.org/xerces-c/apiDocs/class_XMLString.html#d57 states the following: The returned buffer is dynamically allocated and is the responsibility of the caller to delete it when not longer n

DOM tree to a file

2001-08-15 Thread SAMY
I am trying to save DOM tree to a file and a string. thanks JS - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: problems with "carriage return" and "line feed"

2001-08-15 Thread Hal DeVore
> On 14 Aug 2001, "Jason" == Jason E. Stewart wrote: Jason> Also adding a xml:space="preserve" attribute should Jason> work, too, shouldn't it? Nope. --Hal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

Re: XercesLib and Borland C++Builder 5

2001-08-15 Thread Don Mastrovito
I havn't experienced the corruption. Perhaps the comment pertains to a previous version of BCB. The BCB project manager was always quite buggy with respect to file path handling, but less so in version 5. I left those comments as I found them on the assumption that they have some validity in

Re: XercesLib and Borland C++Builder 5

2001-08-15 Thread Don Mastrovito
Chris, Yes it can. I don't use that feature too often, having the IDE available. In the IDE, select "Project|Export Makefile" from the menu. I've pasted a copy of that makefile below. In a DOS box, set your path to xerces-c-src1_5_1\Projects\Win32\BCB5\Xerces-all\XercesLib. Then execute

Re: XercesLib and Borland C++Builder 5

2001-08-15 Thread Herb Chong
what is the reason that changing from debug to release mode corrupts the project directory settings? i would like to have both debug and release libraries. Herb

Re: XercesLib and Borland C++Builder 5

2001-08-15 Thread Chris Hill
Can C++ Builder 5 gererate a makefile from the project file? This would allow users of Borland's free command line compiler and tools to build Xerces using the same work you've put into the BCB version. Chris At 07:18 AM 8/15/2001, Don Mastrovito wrote: >I've made the necessary changes to Xer

#FIXED, #IMPLIED default attributes

2001-08-15 Thread Paul Emberson
Hi, I'm using a SAX2 parser to parse an XML file with a DOCTYPE definition at the top. When the attributes get reported during startElement(), is there a way to know if they are default attributes in the DTD or written in the XML file itself? Thanks, Paul Emberson

Validation and Element insertion question

2001-08-15 Thread David Bonnecaze
My program reads in an xml data file that is validated against a DTD file. I am trying to migrate to xerces 1.5.1 to fix some of the performance and memory leak problems my program is experiencing. I am having 2 issues with the migration. 1. Validate an Element before adding it to the DOM. In

Re: XercesLib and Borland C++Builder 5

2001-08-15 Thread Tinny Ng
Don, Thanks a lot for the work. If you can zip and post the changes to the mailing list, we are glad to check them in. Just couple of questions: 1. >Modify src\util\Compilers\BorlandCDefs.hpp <- only source code change Is this change generic and applicable to other versions of BCB such as BCB4

XercesLib and Borland C++Builder 5

2001-08-15 Thread Don Mastrovito
I've made the necessary changes to XercesLib 1.5.1 that allow it to be built for Windows using Borland C++Builder version 5. All the changes except for one affect only the project files. Unfortunately, BCB5 uses a different format project file than previous versions. It necessitated creating an

RE: Memory leak when parsing from a MemBufInputSource

2001-08-15 Thread Michael Snebang
Title: Memory leak when parsing from a MemBufInputSource     Yes I have tried to delete memBufIS. It does not solve the problem.   - Michael -Original Message-From: Christoffer Dam Bruun [mailto:[EMAIL PROTECTED]]Sent: 15. august 2001 12:59To: '[EMAIL PROTECTED]'Subject: RE:

RE: Memory leak when parsing from a MemBufInputSource

2001-08-15 Thread Erik Rydgren
Title: Memory leak when parsing from a MemBufInputSource To me it looks like you do a new without a delete.   HERE>>    MemBufInputSource* memBufIS = new MemBufInputSource   Erik Rydgren Mandarinen systems AB Sweden -Original Message-From: Michael Snebang [mailto:[EMAIL PROTECT

RE: Memory leak when parsing from a MemBufInputSource

2001-08-15 Thread Christoffer Dam Bruun
Title: Memory leak when parsing from a MemBufInputSource Hi Michael,   Do you ever delete memBufIS in the for loop ?   /Christoffer  -Original Message-From: Michael Snebang [mailto:[EMAIL PROTECTED]]Sent: 15. august 2001 12:58To: [EMAIL PROTECTED]Subject: Memory leak when

Memory leak when parsing from a MemBufInputSource

2001-08-15 Thread Michael Snebang
Title: Memory leak when parsing from a MemBufInputSource In my program I am using a SAXParser and a MemBufInputSource to parse a XML string. When I repeat this a number of times, it seems to use memory. I am using Windows 2000, MS VC++ 6 sp. 4 and xerces 1.5.1. I have reproduced the probl