Hi All, I sent this to the PMC, but haven't gotten any feedback yet. I wanted to let the xerces-c developers know what I'm requesting as well to get your feedback of how best to merge the two codebases/projects.
Cheers, jas. ---------- Forwarded message ---------- From: Jason Stewart <[EMAIL PROTECTED]> Date: Feb 3, 2006 8:19 AM Subject: Xerces-P and Xerces-C merge by 3.0 To: [EMAIL PROTECTED] Hey, I know we haven't discussed this much lately, but I want to begin this for real. I want Xerces-P to be included with Xerces-C by the 3.0 release. Here is my suggestions: New Directories in Xerces-C: -- We add two new directories in the Xerces-C distribution, Perl/ and SWIG/ these will contain the Perl module components and the generic SWIG interface definitions respectively. Build Process -- Then anyone who wants to build Xerces-P will just download Xerces-C and go into the Perl/ directory and make the perl project like a normal perl module (perl Makefile.PL && make && make test && make install). If libxerces-c.so is not already compiled the perl Makefile will compile it also. Test Suite -- The Perl test harness makes testing Xerces *really* easy. There is already a suite for most of the Xerces classes - but not for all. We should include successfully building Xerces-P and running the perl test suite as a pre-condition for making a new release of Xerces-C. I could use help fleshing out and organizing the Perl test suite to include the pieces I don't quite understand. Other Scripting Languages (Python, Ruby, Tcl, ...) -- SWIG has the ability to generate C++ wrappers for *many* languages (some 20 at last count). If there is an interest in anyone in the Xerces dev group we can extend my SWIG support to their language *trivially*. I have spent a fair amount of time over the last year splitting out the perl-specific interfaces from the generic SWIG interfaces. To add a new language requires defining two methods: one to map from UTF16 to the languages Unicode format, and the second mapping from the languages Unicode format to Xerces UTF16 format. Website Changes -- I think leaving the two sites independent is good. There is enough Perl specific info that it requires it's own space. I'm in the process of moving Xerces-P site to forrest. I'm offering to do the same for Xerces-C. Let me know what you think. jas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
