[pygccxml-development] Cache (was: Re: recent changes to pygccxml\pyplusplus)

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

Roman Yakovenko wrote:
>> With this option pyplusplus generates a temporary header (it seems this
>> is even done in memory so no temporary file is used,
> 
> You are wrong. parser.source_reader_t creates temporal file.

oops, ok.

>> but I haven't
>> inspected the sources that closely, so I could be wrong) and invokes
>> gccxml only once. So it would relieve you from creating the temporary
>> header yourself. The drawback is that this compilation mode totally
>> ignores the cache. :(
> 
> Your thoughts are welcome. The problem I did not solve here is next:
> how I should build the key for cache dictionary? Until now every key we built
> use full file name. If you can build an other key without temporal
> file name, then we can
> implement it. 

Well, instead of passing only one file name to the cache we could simply 
pass all relevant file names to the cache. It would then be up to the 
cache implementation to deal with it and create a proper key...

> Also I don't think we should: 0.5 - 2 seconds do you
> think it will make the difference to you?

Well, it's 12s vs 2s for me, so it still gives a little bit of 
performance. But you're right, it's not top priority anymore and I am 
already at those 2s with the current version (by still using 
FILE_BY_FILE and creating a temporary header myself).
I might get back to it once I'm able to create my bindings again and all 
the "top priority" issues have been dealt with. :)

- Matthias -