> No offence meant, but IMHO you'd be way better of if you'd not use > templates for new files, but instead enforce a common coding style > through a source code pretty printer and share the syntax rule file > for that. > Then always before committing to the central repository you could run > the code through that to get lost of developer specific favourite > formattings etc. > Also every developer can have their own little variations for their > convenience and still commit in the same format.
What is important is the result, not the path you have to follow in order to get it :) The only problem with your proposed approach is that you have to set up some Subversion triggered formating. IMO, it's also quite useless : most of the developpers will follow the common rules as soon as they have been adopted. Anyway, it's not really important. What is is to get a source we can compare when merging or doing a diff, without being confronted with thousands of differences because someone use tabs and others use spaces, or brackets have been moved around to please each developers :) -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
