On December 8, 2003 02:52 pm, Lionel Ulmer wrote:
- write a tool that checks the source code for correct tabbing and
rejects the patch if it does not follow THE RULES
Again, not feasible -- I for one edit wine stuff from multiple boxes, multiple editors, I don't want to have to learn how to setup editors on every box I move to.
- or even better, write a re-tabulator which produce source code
following THE RULES (tool that would be applied to all source code on each commit).
This is a real bad idea. We had that we trailing whitespace, and it was a nightmare because CVS would detect that as conflicts so it was sooo hard to work with: submit, wait for Alexandre to commit, update, understand/resolve conflitcs. And for large changes, you can only do cvs up -C, which means you can't keep working until Alexandre commits. Too nasty for words.
We can argue till the cows come home, but I think we've lost track of the purpose. Are we trying to make our lives more difficult? If so, we're on the right track :) Is this 'problem' (that we're creating) worth dealing with all this complication? For what purpose?