John Griessen said: > Let's generate some ideas and constructive criticism now.
Has anyone looked at SWIG? (disclaimer: I've never used it myself, I just think it looks nifty.) > Guile is part of gschem and probably hard to rip out. Yes, but the situation isn't going to get better on its own. The effort spent tracking down stupid version-related problems in guile could well be diverted to alternate scripting solutions. > I can see how some benefit may > come from using a lisp-like script language, since Cadence does in their > chip design layout tools and someone with Cadence script experience may > contribute more easily to gschem. So what are ways to keep it with > little pain? There has been some healthy discussion on the merits and drawbacks of various scripting languages. But, if I'm reading all of the SWIG documentation correctly, one conversion to SWIG gives us access to everything mentioned here: http://www.swig.org/compat.html#SupportedLanguages Thoughts? Has anyone had experience with incorporating SWIG into a mature project? -- Charles Lepple <[EMAIL PROTECTED]> http://www.ghz.cc/charles/
