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

[David Abrahams]

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

> On 18 Sep 2003 at 14:32, David Abrahams wrote:
>
>> > - Always generate an intermediate Python layer with full, automatic
>> > keyword support and a copy of the documentation embedded in the C++
>> > code.
>> 
>> 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?"
>
> 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?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com