Re: [pygccxml-development] parse time with large projects
Brought to you by:
mbaas,
roman_yakovenko
|
From: Roman Y. <rom...@gm...> - 2008-02-28 15:39:17
|
On Thu, Feb 28, 2008 at 5:21 PM, Kevin Watters <kev...@gm...> wrote:
> I'm using "cache = directory_cache_t('cache')" in my module_builder_t
> constructor, and it does cut down on the parse time that would
> otherwise occur, but it still takes around 10 seconds for each .h
> file--and since my project is only growing in size, the time it takes
> to get through all the header files is becoming prohibitively long.
>
> Before I go hacking on the cache stuff, I wanted to ask here--is there
> a specific reason why the hash of a header file, plus all the
> preprocessor defines and include paths, are not enough to recognize an
> already parsed header file? Recognizing these should be an operation
> that takes less than a second, I would think--but some of them take as
> long as ten.
>
> Does anyone else have any suggestions on cutting down the turnaround
> time for a growing Py++ project?
I am: http://language-binding.net/pyplusplus/documentation/how_to/best_practices.html
HTH
--
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/
|