From: aa8vb at vislab.epa.gov (Randall Hopper)
Date: Tue, 6 Apr 1999 14:34:12 GMT
Subject: SWIG, Modulator, BGEN, etc. - which?  (Re: swig or not to swig ?)
In-Reply-To: <3709f149.2262513@news.oh.verio.com>; from Kevin Dahlhausen on Tue, Apr 06, 1999 at 11:39:03AM +0000
References: <4p6O2.1348$8m5.2126@newsr1.twcny.rr.com> <kZ6O2.1351$8m5.2222@newsr1.twcny.rr.com> <gm7O2.1356$8m5.2172@newsr1.twcny.rr.com> <3709f149.2262513@news.oh.verio.com>
Message-ID: <19990406103412.A869943@vislab.epa.gov>
X-UID: 248                                                  

"Darrell" <news at dorb.com>:
 |Didn't have much luck with bgen.
 |modulator seems handy, Is there a reason to prefer swig ?

I'm also interested in what wrapping options folks like best.
Roll-your-own, SWIG, Modulator, BGEN?  (Do others not listed exist for UNIX?)

I'm primarily thinking in terms of both ease of definition and maintenance.
With maintenance, I have in mine:

  1) automatically updating the wrapper "guts" most of the time, and 

  2) ideally providing some facility to "flag" wrapper functions whose 
     signatures have changed.

The latter point is intended to be a work queue for a human operator to act
on.  That is, for them to update the all the scripting code which uses
functions/symbols whose signatures have changed (a substitute for compiling
and linking, since our script isn't compiled and linked with the wrapped
code).

Any pointers or insights appreciated,

Randall




