Hi Christophe,
A couple of things:
1. Did adding XALAN_XALANDOMCHAR_USHORT_MISMATCH solve any problems?
2. It looks like you're working from older source code. Did you get the
latest from CVS to do the port, or are you working from the 1.1 code?
If you haven't gotten the latest, it will be much easier if you do that.
It makes diagnosing problems easier, and means that we can integrate the
changes much more quickly/
3. There are some #defines that we should be able to get rid of from the
Borland header file, but for the time being, a copy of the Visual C++
one is just find.
Now, as far as the error is concerned -- there should be no problem with
finding a match for that function. A couple of things to try:
1. Try adding:
#include <PlatformSupport/DOMStringHelper.hpp>
with the other PlatformSupport includes. This shouldn't be necessary,
but it's worth a try.
2. I have a feeling the Borland compiler is confused. It should be
matching the following substring() overload in DOMStringHelper.hpp:
XALAN_PLATFORMSUPPORT_EXPORT_FUNCTION(XalanDOMString)
substring(
const XalanDOMString& theString,
unsigned int theStartIndex,
unsigned int theEndIndex = unsigned(-1));
Try the following two variations and see if one of them fixes the
problem:
225: if (startsWith(theName, DOMServices::s_XMLNamespaceWithSeparator) == true)
226: {
227: thePrefix = substring(theName,
DOMServices::s_XMLNamespaceWithSeparatorLength, unsigned(-1));
228: }
225: if (startsWith(theName, DOMServices::s_XMLNamespaceWithSeparator) == true)
226: {
227a: unsigned int theStartIndex =
DOMServices::s_XMLNamespaceWithSeparatorLength;
227b
227c: thePrefix = substring(theName, theStartIndex);
228: }
Dave
"Christophe
PARIS" To: <[EMAIL PROTECTED]>
<christophe@epi cc: (bcc: David N Bertoni/CAM/Lotus)
stema.net> Subject: Re: Compilation under Borland
C++
Builder 5
07/11/2001
01:45 AM
Please respond
to xalan-dev
Ok here the modification I've made :
PlatformDefinitions.hpp :
> 61: #if defined (__BORLANDC__)
> 62: #include "BCPPDefinitions.hpp"
> 63: #elif defined(_MSC_VER)
I've created a file BCPPDefinition.hpp (copy of VCPPDefinition.hpp)
and added :
#define XALAN_XALANDOMCHAR_USHORT_MISMATCH
Here the error I have :
[C++ Error] ElemLiteralResult.cpp(227): E2285 Could not find a match for
'substring(const XalanDOMString,const unsigned int &)'
line 227 of ElemLiteralResult.cpp is
225: if (startsWith(theName, DOMServices::s_XMLNamespaceWithSeparator) ==
true)
226: {
227: thePrefix = substring(theName,
DOMServices::s_XMLNamespaceWithSeparatorLength);
228: }
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 9:53 PM
Subject: Re: Compilation under Borland C++ Builder 5
> If you post the errors, perhaps we can help diagnose them. One thing
> that's likely is you're missing some of the appropriate defines from the
> compiler definitions file. I assume you copied the Visual C++
definitions
> file and used it as a model for the C++ Builder one? Why don't you post
> the contents of that file?
>
> At the very least, you must make sure that
> XALAN_XALANDOMCHAR_USHORT_MISMATCH is defined, since Borland's wchar_t is
> not compatible with our XalanDOMChar type.
>
> Dave
> I'm trying to compile Xalan under C++ Builder 5 but I have a lot of
> problems with wide characters in the XalanDOMString implementation.
> Strange because Xerces 1.4.0 compile well.
> Christophe PARIS