On Fri, 16 Apr 2004, Christian Bednarek wrote: > On Thu, 15 Apr 2004 09:17:24 -0500 (CDT), Bob Friesenhahn > <[EMAIL PROTECTED]> wrote: > > > Since LCMS already has a Python extension, and this extension is built > > using SWIG, how does the Tcllcms extension compare? SWIG is also able > > to output scripting interfaces for Tcl, Perl, and a number of other > > scripting environments. > > What would I need to switch from python to tcl? That's more than changing > -python to -tcl in SWIG's commandline :)
I don't know the answer to this, but I suspect that part of the answer may be found in SWIG's documentation. More than likely most of the SWIG part of the effort is handled by changing the SWIG language option as you describe, but there would still be work related to finding the Tcl install, building the extension using the right options, and then installing the extension in the right place so Tcl will find it. For some reason a lot of people claim to not like SWIG (I don't know why), but apparently it works, and Tcl is a simple language so it is unlikely that language nuances would be lost by using SWIG. A dedicated volunteer could modify the lcms package so that SWIG-based extensions may be built and installed for Python, Tcl, Perl, and Ruby. Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Lcms-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/lcms-user
