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

[Prabhu Ramachandran]

>>>>> "ND" == Niall Douglas <s_sourceforge at nedprod.com> writes:

    >> These aren't so drastic; I've been saying things like this for
    >> several months.  However, you might ask yourself "why not just
    >> use SWIG?"

    ND> Bottom-up projects like SWIG easily get success with simple
    ND> C++ but will find it geometrically harder to add increasingly
    ND> complex C++. I went with boost.python because it seemed to me
    ND> to be naturally more easily extendable for advanced C++

Having used both tools I find that hard to believe.  SWIG from CVS
handles quite complex C++.  AFAIK the only thing it does not support
yet is nested structures/classes.  True, Pyste files are Python files
and interface files are not but the SWIG pre-processor is quite
powerful.

  http://www.swig.org/Doc1.3/Preprocessor.html

You might also want to look at this:

  http://pwig.sourceforge.net

which is SWIG wrapped in SWIG so you can use it from Python.

    ND> features. Also, pyste looked very attractive whereas SWIG
    ND> requires custom written interface files which would take me
    ND> weeks to write initially and a high quantity of maintanence
    ND> time whenever the underlying library was changed (often).

Huh?  Pyste files and SWIG interface files are really quite similar.
You need to write the interface files for both and both will need
changing if the underlying library changes.  I don't see how you avoid
that by using Pyste instead of SWIG?

cheers,
prabhu