;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

`
>always write one statement per line as a matter of convention
>still need to put a semicolon at the end of the line
>it's 2012 and everyone has baby duck syndrome about a shitty hack meant to help parsers from the 1960s

>>38
Autoindent this! *grabs dick*

class A:
def __init__(self, x):
def f(x):
if x:
return x
return x
def g(y):
return y

>>38
proportional sans-serif fonts with auto indent.
If you have some way of configuring emacs for this, I want to hear it.

The only reason why it's not a full stop is the latter easily confused with the decimal point.

Statement terminators are there for a reason: to let you know when the end is. People naturally ignore newlines because it is normal to simply continue reading onto the next line once reaching the end of the previous line. Having something visible to delimit individual statements makes things clearer.

>>43
:set number

problem solved


☞ def main ☾ ☽
  ★ if lol
  ☆ ★ puts "Hello World"
  ☝ end

>>43
Douglas Crockford commented in his Javascript videos about how the option of leaving semicolons out of Javascript was a mistake. I disagree with him only because Javascript is such a lax language meant to do simple tasks, but I would agree with him in a complex systems language.

>>41
I said the opposite: it's trivial to put terminators / blocks on FIOC code.

>>42
Unfortunately, Emacs indentation is also based on fixed width chars.
It isn't impossible, but you know how people are avert to changes.

>>43
Newlines are visible, but you know, most people work on a 80x25 tty with 8 spaces/tab, 5 indentation levels and lots of long argument lists / ?: per line... So of course you need line-wrap safe visual clues.

I agree, OP. It's funny how a compiler error might say "missing semicolon at line 145," instead of just modifying the source for you.

>>48
See >>14. You don't want the compiler to fix your errors unless you're a hardcore INTERCAL programmer.

>>41
fuck you!