[OpenAFS] building swig based interfaces
Sun, 01 Sep 2013 14:15:37 -0700
G=C3=A9mes G=C3=A9za <firstname.lastname@example.org> writes:
> The advantage of the swig approach is not just speed, but the ability (I
> don't plan to exploit it) to use the same interface for many more
> languages. Although writing native python bindings were and still are
> under consideration too.
Right, SWIG is basically a way of quickly exposing the C library
interface, without many modifications, to a bunch of different languages.
The more satisfying approach for a developer within a particular language
is to have custom bindings for that language that fit the semantics of the
language and feel "native," which you won't get from SWIG except in some
simple cases. But it's only satisfying if someone actually does that. :)
SWIG tends to be a lot faster to get started with.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>