|
From: Roman Y. <rom...@gm...> - 2006-10-16 06:27:52
|
On 10/15/06, Allen Bierbaum <al...@vr...> wrote: > I agree that this it outside the normal usage scenario for py++, but I > just thought of a reasonable way for the user to think about this in a > way that may be useful to many more people. > > Namely, I was thinking that if the user exposes a class Derived but the > class Base is not exposed, I think it would be reasonable for Py++ to > automatically expose all the methods of Base in Derived. This seems > like a fairly reasonable usecase because there may just be some times > that users only want to expose a couple of classes and don't want to > expose all of their base classes. I am not sure whether it is reasonable or not. It is very easy to implement it in Py++. To tell you the True the functionality like this already presents in Py++: http://language-binding.net/pyplusplus/documentation/apidocs/pyplusplus.decl_wrappers.class_wrapper.class_t-class.html#redefine_operators It could be extended to member functions too. You are welcome to prepare patches and unit test and I will commit them after this release. > What do other people think, is this a common enough usage to make a > feature request out of it? There is more interesting use case, that I would like to support: Lets say that you already have hand written code for base class and now you want to export derived one, using Py++. It could be nice if Py++ would support such mixes. -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |
