Peoples,
This came up a couple of weeks ago. The general consensus was that it should be put into the xalan-dev list, which I agreed to do and then got myself completely side-tracked. (Jason - many apologies.)
Note that Jason is a busy man, so there is going to need to be some help from others. My understanding is that once the basic stuff is set up it should be reasonably easy to port from version to version.
I reckon a big +1 from here. My spare bandwidth is rather limited at the moment, but I'd be happy to help where I can.
Thoughts? +/-?
Cheers,
Berin
-------- Original Message -------- Subject: Adoption of XML::Xalan into official Apache status Date: 10 Jun 2003 15:24:55 -0600 From: Jason E. Stewart <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED]
Hey All,
Xerces-C has an official perl port, Xerces-P (XML::Xerces - in the Perl universe) . There is already a perl port of Xalan-C, XML::Xalan, but it has no representation at xml.apache.org. We'd like to see it included, and would like to know how to proceed.
The approach taken with Xerces is to automatically wrap the C++ codebase using SWIG (www.swig.org) to generate the Perl module and the C++ glue code. SWIG theoretically enables this work to be applied to *any* scripting language, not just Perl - it currently supports around 10 different scripting languages.
Perhaps the ports are better represented not as seperate modules within the xml.apache.org framework, but instead as part of a 'ports' section within the parent C++ project. By making the necessary SWIG interface pieces as generic as possible we could hopefully garner more ports (to say Python, Ruby, Guile, etc.) and thus more support for the parent projects.
Any thoughts, ideas, suggestions?
Cheers, jas. (Xerces-P maintainer)
