on 8/29/01 12:53 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED]
wrote:

> 
> Can you post a small snippet of some of the compiler errors?  All of the
> equals() functions in DOMStringHelper.hpp are global functions while all of
> the equals() functions in XalanDOMString.hpp are member functions, so I
> don't understand what ambuguities there could be.
> 
> The purpose of the DOMStringHelper stuff was to allow us to use multiple
> XalanDOMString implementations.  That's pretty much a thing of the past,
> and we will transitioning away from it, but that is a long-term goal.
> 
> Hope that helps...
> 
> Dave
> 
> 
> 
> 
> Manuel Barros    
> <[EMAIL PROTECTED]         To:      <[EMAIL PROTECTED]>
> om>                      cc:      (bcc: David N Bertoni/CAM/Lotus)
> Subject: Porting Xalan to Codewarrior using MSL
> 08/29/2001 11:33 
> AM               
> Please respond   
> to xalan-dev     
> 
> 
> 
> 
> 
> Hello,
> 
> 
> I am trying to port Xalan C++ to the Macintosh using Metrowerks Codewarrior
> and MSL (Metrowerks STL).  I find ambiguous equals() compile time errors.
> The compiler cannot figure out which equals() to call, it does not know if
> it should call the one in DOMStringHelper.hpp, or the one defined in
> XalanDOMString.hpp.
> 
> I would like to have some insight on the purpose of DOMStringHelper and
> XalanDOMString.  These two files seem to work together, but I am unsure
> how.
> A better understanding  Obviously, other compilers do not seem to have this
> problem.
> 
> -- Manuel A. Barros
> 
> 
> 
> 
> 
> 
> 

This is one of the error messages I get from CW:

Error   : ambiguous access to overloaded function
'XalanDOMString::equals(const XalanDOMString &, const XalanDOMString &)'
'equals(const XalanDOMString &, const XalanDOMString &)'
DOMServices.cpp line 566              s_XMLNamespaceWithSeparator);



This is the code that causes it:

                    const bool isPrefix = len <=
s_XMLNamespaceWithSeparatorLength ? false :
                            equals(substring(aname,
                                             0,
                   
s_XMLNamespaceWithSeparatorLength),
                                   s_XMLNamespaceWithSeparator);

I can fix it by forcing it to use XalanDOMString namespace, but this is
unsatisfactory.  It may be that CW has problems resolving namespaces.


-- Manuel

Reply via email to