But, only sip knows what files will be generated because it depends of the input sip file(s) content. Moreover, only sip knows the exact structure of the comments it adds at the begining of each file. This comments must not be taken into account when comparing files (it contains date). If the comment structure is changed in sip, the comparison algorithm must change. This is why I think that this modification has something to do with what sip does.

On 2/28/06, Phil Thompson <[EMAIL PROTECTED] > wrote:
On Tuesday 28 February 2006 3:10 pm, Yann Cointepas wrote:
> Hi,
>
> What is the procedure to propose modification to sip ?

You've just followed it. :)

> I need a feature
> that I am ready to program. I would like sip to have an option to generate
> a C++ file only if it does not exists or if it is different from the
> existing one. This would greatly improve compilation time (using make
> dependencies for instance) when modifying a small part of a sip project. I
> looked at the code of sip 4.3.2 and it seem that there is not so much work
> to do. I am ready to:
>
> - Describe the changes I would like to do
> - Implement these changes in whatever sip version is appropriate
> - Give (for free) these changes to sip developpers
>
> Tell me if it can be useful for other people, otherwise I will keep using a
> Python script that generate the sip files in a temporary directory before
> copying only modified ones.

I wouldn't accept this change as it doesn't really have anything to do with
what SIP does (although I readily admit that some of SIP's existing
functionality also falls into that category).

My recommended solution would be to use some sort of wrapper as you are
currently doing. You could always put it on the Wiki.

Phil



--
Yann Cointepas            Tel: +33 1 69 86 78 52
CEA - SHFJ                  Fax: +33 1 69 86 77 86
4, place du General Leclerc
91401 Orsay Cedex France
_______________________________________________
PyKDE mailing list    [email protected]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

Reply via email to