Thank you all for all of your help

I would like to say thanks to everybody in this group that has helped me out. Xerces is one of the best XML libraries I have ever worked with and probably has become the one that I'm going to use in all of my projects (if I can find out a way to use it in Visual Basic). __

DOCTYPE problems

Hi All, I couldn't find the Xerces-c user list so I am posting to this list. I am trying to include http://xml.bla.de/2.0/BLAxml.dtd";> into a dom document that I am building. After doing this: DOMDocumentType * dType = impl->createDocumentType(X("BLAxml"), X(""), X("http://xml.bla.de/2.0

DO NOT REPLY [Bug 17983] - Formatter does not escape control characters

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: XMLPlatformUtils::compareAndSwap fn

I dont want to beat this thing to death. But just feel that we could deal with win95 as a special case rather than forcing ALL windows versions to use a hack that is meant for just win95. there is nothing like "when win95 dies". it will never die. we cant stop someone somewhere from running wi

Re: Compiling on Mac OS 9

Magnus, There are a couple of "solutions" to your question: Okay: use the perl code in "ShortenFiles.pl" that is supplied in the Mac OS projects directory to automatically shorten the file names. Note that the current CW project files assume long names, not short

RE: XMLPlatformUtils::compareAndSwap fn

Hi Vinayak, The comment is explicit about why the ifdef is there: // If you are willing to give up Win95 support change this to #if 0 // otherwise we are back to using assembler. // (But only if building with compilers that support inline assembler.) In other words, some day,

RE: XMLPlatformUtils::compareAndSwap fn

I think the point we're making is that the call to InterlockedCompareExchange that is in that code will never happen since the first part of the #ifdef is always satisfied for all windows platforms because _MSC_VER is always defined. I believe Borland even defines it. So the suggestion would be t

RE: XMLPlatformUtils::compareAndSwap fn

> The whole point of the ifdef is that all Windows builds use the inline > assembly code. Got it. But then all we needed was #ifdef WIN64 InterlockedCompareExchangePointer(..) #else assembly code #endif Because this entire class (under Win32PlatformUtils.cpp) is going to be used only by window

Re: XMLPlatformUtils::compareAndSwap fn

The whole point of the ifdef is that all Windows builds use the inline assembly code. The ifdef is checked at compile time, but the assumption is you would want to build on NT or Win2000, but run on Windows 95. Dave

RE: compilation problems - Xerces C++ 2.2 32 bit Binary for Windows

Your absolutely right. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Friday, March 14, 2003 11:21 AM > To: [EMAIL PROTECTED] > Subject: RE: compilation problems - Xerces C++ 2.2 32 bit Binary for > Windows > > > You may have a point here. But, Michael i

RE: compilation problems - Xerces C++ 2.2 32 bit Binary for Windows

You may have a point here. But, Michael is compiling the branch that uses InterlockedCompareExchangePointer because he has defined WIN64. If he really is using WIN64 then he doesnt need to have platform SDK to get this Fn. Installing the platform sdk may solve this one problem for him, but he ma

XMLPlatformUtils::compareAndSwap fn

I was just following up on my previous reply and was puzzled by the implementation of this fn. XMLPlatformUtils::compareAndSwap( void** toFill , const void* const newValue , const void* const toCompare) { #if defined WIN64

RE: compilation problems - Xerces C++ 2.2 32 bit Binary for Windows

Vinayak, Michael Actually InterlockedCompareExchangePointer is available in Win32. Look at the MSDN doc again. We use it here all the time on Win32. But yes, what MS does is wrap InterlockedCompareExchange for win32. What Michael may want to do is download the Platform SDK from Microsoft. It is a

Compiling on Mac OS 9

Hi, I would like to know if anyone knows which of the of the files in Xerces-C havbe filenames longer than 31 chars? So I can change them and the CodeWarrior project xml-file and compile it on Mac OS 9. Regards, Magnus Strand -

Re: Trouble Building

--- David N Bertoni/Cambridge/IBM Number 1 was the culprit. Thanks! -exits > > Two things to try: > >1. Set XERCESCROOT instead of XERCESROOT -- or > does your posting contain >a typo? > >2. Use runConfigure instead of configure. > > See the build instructions for more info: >

Re: Trouble Building

That was the problem. Thanks! --- Gary Hughes <[EMAIL PROTECTED]> wrote: > You need to set 'XERCESCROOT' not 'XERCESROOT'. > > Gary. > > exits funnel wrote: > > Hello, > > > > I apologize if this is not an appropriate topic, > but > > I've just downloaded the xerces source and I'm > having > >

RE: compilation problems - Xerces C++ 2.2 32 bit Binary for Windows

InterlockedCompareExchangePointer is a Win64 function. I have a strong hunch that you have defined Win64 by mistake... The win32 counterpart is the function InterlockedCompareExchange(). -Vinayak > -Original Message- > From: Stanitis, Michael [mailto:[EMAIL PROTECTED] > Sent: Friday, M

Bug 17945: Allow custom implementation of DOMNode interface to enable reference counting over nodes

Title: Bug 17945: Allow custom implementation of DOMNode interface to enable reference counting over nodes Hi all, Can somebody with CVS check in privileges please have a look at the change proposed, and tell me if it will be checked in for the next release? If not, let's start a discussion

compilation problems - Xerces C++ 2.2 32 bit Binary for Windows

When I try to compile Xerces Lib, I get an error: xerces-c-src2_2_0\src\xercesc\util\Platforms\Win32\Win32PlatformUtils.cpp(81 3) : error C2039: 'InterlockedCompareExchangePointer' : is not a member of '`global namespace'' I have tried to resolve this problem, but haven't had any success. Micro

Re: Error

Two things: 1. I added XERCES_CPP_NAMESPACE_QUALIFIER and it still didn't seem to help (cut and paste it exactly out of the article that way) 2. I finally fixed that problem and now it works great. Thanks for all of your help. At 09:51 AM 3/14/2003 +0200, you wrote: > "Kohli, Naveen" wrote: > >

Re: xerces-com.dll build problems in 2.2.0

At 08.23 14/03/2003 -0500, you wrote: What a coincidence! I have also just fixed the COM files in CVS to have it compiled. But since I have no knowledge of COM at all, please help to verify its functionality. I refreshed the code from CVS, rebuilt the COM project, and tested using the test fou

Re: xerces-com.dll build problems in 2.2.0

What a coincidence! I have also just fixed the COM files in CVS to have it compiled. But since I have no knowledge of COM at all, please help to verify its functionality. Thanks! Tinny - Original Message - From: "Alberto Massari" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Frid

DO NOT REPLY [Bug 17147] - C++ namespace breaks build of XercesCOM DLL

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 17215] - Build fails on xml4com project (VC6 compiler)

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 17147] - C++ namespace breaks build of XercesCOM DLL

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 17886] - Can not compile xercesc-com

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 17147] - C++ namespace breaks build of XercesCOM DLL

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: xerces-com.dll build problems in 2.2.0

Yes, the COM files haven't been updated to use the namespace qualifier; try unzipping the attached ZIP file in the src\xercesc\com directory and rebuild. Alberto At 10.49 14/03/2003 +, you wrote: Hello All, I have a problem with with building xerces-com.dll (COM wrapper on Windows) for the

xerces-com.dll build problems in 2.2.0

Hello All,   I have a problem with with building xerces-com.dll (COM wrapper on Windows) for the current Xerces version 2.2.0 . I get multiple errors (total is 93) when compiling xml4com, e.g:   F:\wa\Xerces\src\xercesc\com\IXMLDOMNodeImpl.h(115) : error C2143: syntax error : missing ';' be