[C++-sig] Pyste: feature requests

[Nicodemus]

Hi Prabhu,

Prabhu Ramachandran wrote:

>Hi Nicodemus,
>  
>
>    N> I see. Unfortunately this breaks backward compability. 8/ But
>    N> notice that Pyste only overwrites files if they changed,
>    N> otherwise it leaves them intact, so as to not disturb build
>    N> systems out there that depend on time-stamps.
>
>Yes, I noticed the SmartFile while poking around.  Neat.
>
>If backwards compatibility is the problem you could always define a
>new option that does not interfere with the current working.
>Something like this:
>
> --only-wrapper 
>             for individual files with only the export functions
>             and without generating the module code.
>
> --only-main 
>             for the main module.cpp file that calls the exports and
>             initializes the module.
>

Yeah, it is an option too.

>    N> I think a good option would be something like
>    N> --xml-cache=<dir>, where Pyste would get the generated gccxml
>    N> files, or write them there in case they are not found. The
>    N> bottleneck with Pyste is always GCCXML, since it has to
>    N> basically compile the source files. What do you think?
>
>Yes, that also sounds OK to me.  If the wrapper-generation time will
>drop and not every single file will be re-parsed/compiled and wrapped
>then I'm OK with a --xml-cache option.  
>  
>

Great, I will implement that then.

>Basically, the trouble is that with many .pyste files its a pain
>changing just one Pyste file and waiting for a long while for pyste
>(gccxml actually) to finish.
>  
>

I understand.

>The other desireable feature would be to dump only one file per .pyste
>file.  This makes dependencies with something like SCons a non-issue.
>If not its hard to figure out which files depend on what.  Again if
>backwards compatibility is a problem perhaps another option --one-file
>needs to be added.
>
I am working on this right now. 8)

Regards,
Nicodemus.