On Sep 21, 2008, at 1:30 PM, Olin Lathrop wrote:

> Peter Loron wrote:
>> Yes, you can help the programmer along by forcing these restrictions
>> or conventions into the language/interpreter/compiler. However, I
>> prefer to push that out to the next layer up.
>
> You haven't given any example, so this still sounds like the you're  
> running
> into the tool catching you making a mess, and you're complaining  
> because
> you'd rather be lazy and make a mess than to do it right.  Once  
> again, can
> you provide a example code that you feel should be allowed but isn't?

Part of it is simply stylistic. I prefer to use braces to define  
nesting. My beef with Python is that there is one way to do it,  
Guido's way. If you are using braces to indicate nesting, you can  
place them in many different ways. 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  
(you _are_ using a version control system, aren't you?) or as part of  
your build system.

Some people will slack off on some details given an environment that  
lets them get away with it. Thus the checks before the work is allowed  
to enter the system. You have a few choices:

1. Hire perfect coders that always write perfect code.
2. Have the language syntax enforce formatting.
3. Have tools that review the code and enforce rules on formatting, etc.
4. Don't bother.

#1 is impossible. I've tried. Some folks (myself included) feel that  
#2 is restrictive. #3 is what I am most familiar with and have seen it  
work at many companies. #4 is a train wreck waiting to happen.

In my opinion, you need to have checks done on code no matter what the  
language, so you may as well put the syntax and formatting enforcement  
there.

-Pete
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist