colostomy

[Cliff Crawford]

* Dirck Blaskey menulis:
| 
| Please, PLEASE make colon's optional when not needed.
| After more than a year, I still frequently type this:
|     if condition    # or def or while or for etc.
|         do something
| 
| instead of
|     if condition:
|         do something
| 
| As long as the block isn't on the same line
| ( if condition: do something )
| the colon isn't necessary, an end-of-line should be sufficient.

I actually like the colons.  They seem to make code a little easier
to read.


| I waste a lot of time going back and filling in the bloody things.

After I learned Python, I had the same problem at first with C and
semicolons.  I'm not sure why I hate semicolons as EOL markers, but
like colons as block markers; I guess one is too much redundancy
while the other is just the right amount. <g>


| The only other suggestion I have, and this isn't nearly as important:
| it would be nice to have block comments like c's /* */ to be
| able to add a multi-line comment quickly outside of the
| doc strings.

You can enclose the comment in """...""".  You can have strings
anywhere where a statement is expected.


-- 
cliff crawford    -><-    http://www.people.cornell.edu/pages/cjc26/
                                                       icq 68165166
"IS I yes wardrobe yield [the] evaluation."     member of A.H.M.A.D.