[C++-sig] Re: Boost.Python: few thoughts and questions...

[David Abrahams]

Nicodemus <nicodemus at globalite.com.br> writes:

> David Abrahams wrote:
>
>>Roman Sulzhyk <roman_sulzhyk at yahoo.com> writes:
>>  
>>>Also, when I'm exposing a class, I think it would be nice to expose all
>>>of the virtual methods inherited from base classes, even if they're not
>>>explicitly overloaded in the class itself
>>>    
>>             ^^^^^^^^^^
>>"Overridden" again?
>>
>>And why only virtual functions?  I'd be really surprised if Pyste
>>failed to expose *all* of the functions publicly inherited from base
>>classes but if that's the case, it should probably be fixed.
>>  
>
> Pyste does not export the base's member functions in the derived
> class. If the user wants functions from the base class, he should
> export the base class too. Perhaps this behaviour should change?

Often base class partitioning is merely an implementation detail.  It
seems to me that if public bases are not explicitly exported they
should be exported implicitly, unless explicitly suppressed.

But I might be wrong about that.

>>BTW, "methods" is a Python term; the C++ term is "function" or "member
>>function".  When discussing two languages at once it gets really
>>confusing if you're not very careful with terminology.

So you might want to tweak the Pyste docs accordingly ;->

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