[C++-sig] Re: [Implementation] Calling wrapped functions, converters, policies

[Niall Douglas]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18 Sep 2003 at 17:32, David Abrahams wrote:

> > Bottom-up projects like SWIG easily get success with simple C++ but
> > will find it geometrically harder to add increasingly complex C++. I
> > went with boost.python because it seemed to me to be naturally more
> > easily extendable for advanced C++ features. Also, pyste looked very
> > attractive whereas SWIG requires custom written interface files
> > which would take me weeks to write initially and a high quantity of
> > maintanence time whenever the underlying library was changed
> > (often).
> 
> What's the difference between custom-written interface files and
> custom-written Pyste scripts?

pyste scripts are way, way shorter. SWIG interface files are a 
simplified duplicate of the C++ header - that IMHO is stupid because 
every time the header file changes, you must mirror the changes in 
the SWIG interface file.

Way I've set it up, I have a python script which inspects the C++ 
project and generates lots of pyste files using another config file 
written in python which customises pyste config file generation for 
each C++ header file. Then pyste spits out boost.python wrappers. 
Then, theoretically, boost.python compiles into a DLL.

This way the C++ project can dramatically change, and all I need to 
alter at most is the customisation per header config file and often I 
don't need to alter anything at all. Very sweet for maintanence 
costs.

Cheers,
Niall





-----BEGIN PGP SIGNATURE-----
Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2

iQA/AwUBP2oqgMEcvDLFGKbPEQJH1gCgl9ZktjK0CkOOsSBOgG+XwYD2P/kAmwbn
M0p6etOu8xVByk8m/3trMrWG
=0DmR
-----END PGP SIGNATURE-----