On 9/11/06, Matthias Baas <ba...@ir...> wrote:
> Hi,
>
> meanwhile it has come up a few times now in this list, but I believe the
> finalize functionality is not yet in place, is it?
Right.
> What is the current status on this? In particular, what properties will
> control this?
There are no such properties.
> As you might have read already in the other thread from today, the
> function transformation feature on non-virtual functions should
> optionally result in the creation of a wrapper class or not. I'd say
> this basically is already something that can be controlled by the
> finalize functionality. So it would be nice if I could use the same
> attributes/properties that will also be used by the other parts of Py++.
Well, obviously you can not.
Actually "finalize" functionality was never a stopper for use of Py++.
Most users treats absence of "finalize" as small inconvinience.
There are always some other problems that have higher priority. In previous
version it was documentation, indexing suite v2, class_multiplie_file writer and
user feedback. This version the main feature is FT functionality. I
also will add
"add_method" functionality. Thus Py++ will better suited for creating bindings
for project written in C.
There are few features that I have to add to the engine: properties,
iterators and
arrays support using indexing suite v2.
--
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/
|
