26 lines
991 B
Plaintext
26 lines
991 B
Plaintext
From: morse at harborcom.net (Kevin Dahlhausen)
|
|
Date: Tue, 06 Apr 1999 11:39:03 GMT
|
|
Subject: swig or not to swig ?
|
|
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>
|
|
Message-ID: <3709f149.2262513@news.oh.verio.com>
|
|
X-UID: 704
|
|
|
|
>Didn't have much luck with bgen.
|
|
>modulator seems handy, Is there a reason to prefer swig ?
|
|
|
|
Ahh, because it works really well? :)
|
|
Seriously, depending on the library, it can make creating wrappers trivial.
|
|
It can do most of the work itself, you just have to help it with ambiguos
|
|
parameters - like int * refererring to a list of ints or something. Python is
|
|
very well documented on the swig site. Give it a shot.
|
|
|
|
Having said that. I would guess - not having used modulator - that a reason not
|
|
to prefer swig is that you need to compile a shared module. does the modulator
|
|
|
|
produce a pure python source result?
|
|
|
|
|
|
|
|
|
|
|