Lionel Debroux (./4) :
1) I'll keep writing TIGCC/GCC4TI, especially for things that may apply to both code bases.

Those things do not apply to both code bases. I am not interested in the feedback you're collecting at all (especially because your "options" are all non-options for TIGCC).

The compatibility between both code bases will stay good, certainly.

No it won't, because you're about to radically change the IDEs in GCC4TI, changes which TIGCC is not going to make (e.g. completely changing the way projects are built, and also introducing a new incompatible project format), whereas on the other hand in TIGCC, the plan is still to have KTIGCC be the only supported IDE, a move which you are not interested in making in GCC4TI. So the code bases will soon be very different, especially as it comes to the IDE(s).

Please speak for your project only.

2) You don't collect your own data, or at least, you disregard the data (VTI support, etc.).

Indeed, I wrote "if I need it" for a reason. The thing is, I don't need your data.

Stop trying to speak on my behalf.

As for ./3... thanks for giving your opinion
But it's just that, an "opinion". Have you noticed the number of times you wrote "I" in ./3 ?

But obviously it's all correct because you didn't bother replying (except for 2 minor details).

As The_One_Guy and Peter Fernandes (hypersonic) have mentioned on ticalc.org, as maeyhem has mentioned on the TIGCC/TICT message board

Again, please stop speaking on behalf of other people. I'm sure hypersonic won't appreciate you using something he wrote as an argument in your favor, and I really don't see how his only comment in the ticalc.org thread confirms what you're saying in any way.

* as we discussed in another section of yAronet, the behaviour of the TIGCC IDEs wrt. compilation in a temp folder and non-saved files is definitely uncommon for IDEs and build systems.

But it's how TIGCC works and it will not change in TIGCC.

tprbuilder can be modified to check which files have changed and which haven't, in order to avoid rebuilding everything in some cases.

To some extent yes, but it doesn't work for unsaved changes. The IDEs have additional logic to detect unsaved changes as a changed file.

* in France, "format propriétaire" is often used for a format that is understood by a single tool / toolchain. TPR and the help system files belong to that definition.

Call it the way you want, but there's nothing wrong with a "proprietary" format under that definition, the real problems with truly proprietary formats are completely different (obscure binary data which is hard to reverse-engineer, software patents etc.) and don't apply to the TPR format at all.