| HN Mirror

Y	Hacker News new \| ask \| show \| jobs


	by xigoi 1116 days ago
	A parser is something you write once and then it's done, so it shouldn't be the deciding factor. And parsing indentation-based languages is not that hard, just replace indents and dedents with a special token. In a brace-based language, if your braces are wrong, your logic is wrong. How is that better? At least a mistake in indentation is much easier for a human to spot.

1 comments

Run the formatter, and the brace-based mistake is easy to spot too.

So what's the point of having braces if you're going to use indentation anyway?

To do more things with the source than just compile it.

And how do braces and semicolons help you with that?

Exactly what I mentioned above: source formatting is just one of the things you can do with braces and not significant whitespace. [1]

Also, forget a brace in your program, just one, and the compiler can tell.

Forget one indentation? No dice.

And while braces can break things too, editor settings can make it much easier to break things with significant whitespace. [2] [3]

Also, refactoring. [4]

Editor stuff. [5]

Python does have an auto-formatter [6], so clearly indentation doesn't prevent that.

> Also, forget a brace in your program, just one, and the compiler can tell.

Should we duplicate every character, so the compiler can tell if you leave one out? This is not a radiation-hardened quine [7].

> editor settings can make it much easier to break things with significant whitespace.

Then use an editor which doesn't.

> Selecting all code contained in a brace or a parents is so much easier (in vim the % movement) than if you have to walk lines.

I have a plugin for Neovim that adds indentation-based motions. The implementation is trivial.