Peter Loron wrote:
> Part of it is simply stylistic. I prefer to use braces to define
> nesting.

Which is just reiterating that you don't like it because you don't like it.

> My beef with Python is that there is one way to do it,
> Guido's way.

That's precisely the point.

> If you are using braces to indicate nesting, you can
> place them in many different ways.

But this is the mess Python avoids.  You haven't given any argument for why
having many different ways of formatting the same code is a good thing.

> You can achieve the same end-goal
> of helping coders write clear code (or even enforcing rigid code
> standards) by using a pre-commit hook on your version control system
> or as part of your build system.

Why is it OK for the build system to enforce the rules but for the language
not to?  The programmer still has to adhere to them either way.

> 2. Have the language syntax enforce formatting.
> 3. Have tools that review the code and enforce rules on formatting,
> etc.

It seems to me the distinction between these two is of little consequence to
the programmer.  Either way the code ends up adhering to the rules whether
the programmer likes the rules or not.  The advantage of #2 is that the
enforcement is global, not just for your project or site or company.  That
means it will be easier to include code received from other places since it
is guaranteed to follow the same rules, and everyone is used to looking at
and understands the same style.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist