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

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

Allen Bierbaum wrote:
>> I'm not exactly sure which customizations you mean, but I don't think 
>> I'm interfering with your customizations. The only modification to 
>> Py++ that I needed is already checked in (the modification to pygccxml 
>> so that XML files get cached). The actual pruning happens outside Py++ 
>> and doesn't need any further customization.
>>
>> And for the query cache the only customization I needed was to 
>> override the constructor of declaration_t which I can do within my own 
>> code so it's not necessary to modify Py++ itself.
> 
> Ok. The modification I did in goodies was to override the module builder.
> 
> I as not worried at all about interference, I was actually hoping that 
> what you were doing would find it's way into Py++ so I could get rid of 
> my extensions.  I would like to see a way that everyone can see the 
> additional performance of better caching.  I hope to try out some of 
> your performance improvements soon.  I can always find a need for better 
> performance. :)

I still have to commit the changes to pypp_api (where the query cache is 
located). I'm not sure if it would be just as straightforward to 
implement the cache in the official query functions. From the examples 
I've seen so far the regular query functions seem to rely on lambda 
functions more heavily than is done in pypp_api, whose filters are 
rather "value-based" instead of being "function-based". So it is not as 
straightforward anymore to create a unique key for the cache entries 
(i.e. to find out if a particular function that was passed to a query 
operation is still the same as in the previous run). You could probably 
extract the source code of the function and compare that one, but this 
could also break if the function uses another function and only that 
other function has been changed.

- Matthias -