...standardize on a coding style. It's not important
for your co-workers to be able to work on your PC, but it
is important for them to be able to work on your code.
Question: is it practical to let each programmer use
their favourite (and obviously correct (as long as it's
1TBS ;-)) coding style, and let programs like
indent and perltidy "standardize" the
code when it gets checked in? That gives you fewer holy
wars (bracing style, indent depth, tabs vs. spaces, etfc)
but adds an extra layer of complexity. (You'd still have
to standardize on things like naming conventions.) Has
anyone tried this?
The hell with paco, vote for Erudil!