Re: [pygccxml-development] Another way to speed up the generation process...

[Roman Y. <rom...@gm...>]

On 10/20/06, Allen Bierbaum <al...@vr...> wrote:
> >
> >While remove_declarations works as you expect, the functionality is broken.
> >For example: base and derived classes. if you remove base class from the
> >declaration tree, base class still will be accessible from the derived "bases"
> >property. Or if some function takes as argument instance of some class
> >and you remove the class from the declaration tree, the type of argument will
> >continue to keep reference to the class.
> >
> >
> I may be missing something, but those references will still be valid
> correct?  Python won't garbage collect them so it should be fine if
> Matthias removes something from the tree that doesn't need to be
> wrapped.  In the process of wrapping the remaining decls, if there is a
> reference to a removed decl it will still be there it just won't ever be
> wrapped which should be fine since those are the ones being removed
> anyway right. :)

Obviously I am not talking about "dangling references". The order of generated
code and it's correctness could be changed. Just scan decl_wrappers package
and take a look how many times Py++ is scanning the declarations tree.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/