Hi Thomas,

This is certainly something we can take up on the development list, but
it's certainly not appropriate for the user list (by the way, please don't
cross post).  The first thing to do would be to send me privately a tar.gz
with the source code for XML::Xalan and any appropriate build information,
so I can try to reproduce this and see what's going on.  I suspect it will
be related to namespaces.  In particular, forward declaration of Xalan
classes becomes more difficult with namespaces.

Thanks!

Dave



                                                                                       
                                                           
                      "Thomas F.                                                       
                                                           
                      O'Connell"               To:      [EMAIL PROTECTED]              
                                                    
                      <[EMAIL PROTECTED]         cc:      [EMAIL PROTECTED]            
                                                  
                      com>                     Subject: Xalan C++ 1.6 and XML::Xalan 
0.44                                                         
                                                                                       
                                                           
                      09/25/2003 02:48                                                 
                                                           
                      PM                                                               
                                                           
                      Please respond                                                   
                                                           
                      to xalan-dev                                                     
                                                           
                                                                                       
                                                           



A while ago on this list, it was suggested (by David Bertoni) that,
because of the effort to maintain compile-time and binary stability
between successive versions of Xalan C++, it should theoretically be
possible to build the old XML::Xalan Perl wrapper -- originally designed
for Xalan C++ 1.3 -- against Xalan C++ 1.6.

Unfortunately, this turns out not to be the case. I was able to build
ICU 2.6, Xerces C++ 2.3.0, Xerces Perl 2.3.0-0, and Xalan C++ 1.6 all
successfully. Now, trying to build XML::Xalan against Xalan C++ 1.6, I'm
running into compilation issues that are definitely based on changes to
the Xalan C++ source tree. I've looked into the problem a little bit,
but the strange part is that the first error I get in a long chain of
errors is a parser error.

For this to make any sense, you'd have to see the source code for
XML::Xalan. If anyone has the time to take a look, here's the error I'm
currently getting (more comments follow error):

...

Interestingly, if I comment out the namespace directive in
$XALANCROOT/src/xalanc/XPath, the set of errors changes dramatically.

I've tried unsuccessfully to contact Edwin Pratomo, the original
maintainer of XML::Xalan, several times over the past several months.
There's been talk of +1ing XML::Xalan as an official Apache XML Project.
I'd be happy to help with this effort (I'm already trying to help Jason
Stewart with at least the documentation of Xerces Perl).

I figured I'd (cross-)post here to see if anyone more familiar with
Xalan C++ 1.6 internals (or Xalan or C++ in general) might know what's
causing the parser error and other problems.

I've got a detailed build document for the entire Xerces/Xalan suite
(+ICU) for Linux that works for Xerces 2.0/Xalan 1.4 (including
XML::Xalan). I'd be happy to post the version of this that works for
Xerces 2.3/Xalan 1.6 (not including XML::Xalan, unless someone replies
to this post ... :).

Thanks!

-tfo



Reply via email to