Hi Jason, Jason Stewart <[EMAIL PROTECTED]> writes:
> > If we are to keep them in swig then the whole idea of having only > > language-independent part in Xerces-C++ becomes moot since these > > two directories (especially interfaces/Perl) appear to be very > > language-dependent and I would imagine similar directories would > > need to be added for other languages. > > Yes, new language bindings would need to add a directory under > swig/interfaces - e.g. swig/interfaces/Python/, swig/interfaces/Ruby, > etc... > > These are the SWIG interface files that contain language-specific > details - but no language-specific *code* - that is the reason I want > to keep them in swig/ - because they are SWIG files - not *Perl* > files... > > Just to be clear: all the files in swig/interfaces contain macro > definitions like the following: > > #ifdef SWIGPERL > %include Perl/typmaps.i > #endif Oh, that's ugly. I thought SWIG allows one to generate bindings for a specific scripting language from a common, language- independent set of interface definitions (which we could then keep in Xerces-C++). But in reality you need to pepper those interface definitions with language-specific fragments which makes the whole idea of keeping them in Xerces-C++ pointless since we will have to modify those definitions for every scripting language someone wants to support. I would therefore suggest that we move swig out of Xerces-C++ into either Xerces-SWIG or Xerces-P (either way it will be a maintenance nightmare if there is ever more then a handful of scripting languages supported). > If I remove swig/ from Xerces-C completely, then I don't know how I > can build the Makefile for swig/util. The idea was to hook it into the > autoconf system using a --with-swig option for configure. If this can > be handled, then moving swig/ out of Xerces-C and into its own > Xerces-SWIG is OK with me. It will be straightforward to add its own automake setup to Xerces-SWIG that will build the util library. The only thing that needs to be decided is how the Xerces-C++ distribution will be located depending on whether it will be inside Xerces-SWIG or Xerces-SWIG will depend on outside Xerces-C++ installation. I can help setup automake for Xerces-SWIG once this decision is made. Boris -- Boris Kolpackov, Code Synthesis Tools http://codesynthesis.com/~boris/blog Open source XML data binding for C++: http://codesynthesis.com/products/xsd Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
