Re: [pygccxml-development] Status of code inserters

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
>> I haven't committed the code yet because I also did changes to Py++
>> itself (and not only pypp_api or the independent sub-package) and
>> committing everything would put Py++ into an inconsistent state where it
>> would probably break everyone else's projects.
> 
> If I understand right, you have to change: decl_wrappers,
> code_creators packages, right?

Exactly.

> If I don't use new functionality my code should continue to work, right?

Well, I cannot guarantee that because the code generated for public 
virtual member functions would definitely be different than before, even 
if you don't use function transformers. I'm not aware that it would 
break anything but I haven't tested it, so I can't say for sure.

I have just committed those parts that are just additions to Py++ (i.e. 
the new package + the decl_wrapper modification), so this shouldn't 
break anything. The missing part now is code_creators/calldef.py which I 
have attached to this mail. Currently, I have only modified the classes 
mem_fun_v_wrapper_t and mem_fun_v_t (I hope it goes through to the 
list). These classes will now produce the code from the wiki (option 3) 
which is different from the previous code, even when no function 
transformers are in use.

- Matthias -