Re: [pygccxml-development] Status of code inserters

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

Roman Yakovenko wrote:
> Matthias where is the code you are talking about? Do you want to create
> function_transformers package under pyplusplus and move all relevant code
> to it?

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.

Well, I could already commit the new sub-package which is currently 
called "wrapper_substitution" (would you like me to rename it to 
"function_transformers"?) and which contains the base functionality 
(i.e. the base function transformer mechanism + substitution services).
This definitely won't break any existing code. Committing calldef_t is 
also safe as it only adds features but for code_creators/calldef.py I 
would rather suggest to post that file here so that you can inspect them 
without that we get a broken version of Py++ inside the repository.

>> Yesterday and today I have already done the following things:
>>
>> - Added a property "function_transformers" to calldef_t
> 
> Do you mean decl_wrappers.calldef_t, right

Right.

>> (and while I was
>> at it I already added the property "thread_safe" as well)
> 
> Please, remove thread_safe. We will add this later.

Well, my thinking was that even though the features are mostly 
independent from each other they affect the same source code and doing 
them separately means that the very same code has to be touched twice.
Another reason is that this is rather high priority for me because it 
prevents me from doing another release of the Maya bindings (Python 
plugins currently don't work at all when multi-threading is enabled).
But I can leave this attribute only in my local copy for now, that's no 
problem.

- Matthias -