3 ms·

The point of my example was simple - Go's gross mishandling of whitespace is a permanent trap for the unwary and a huge liability for people coming from other l

The point of my example was simple - Go's gross mishandling of whitespace is a permanent trap for the unwary and a huge liability for people coming from other languages. When D was nascent, many people proposed various schemes for making semicolons optional. I think it's great D didn't fall for such.

stcredzero 16y ago
Name one language that doesn't have "a permanent trap for the unwary and a huge liability for people coming from other languages."
- jibal 16y ago
  tu quoque fallacy -- the worst possible form of argument FOR something.
  - stcredzero 16y ago
    Only a fallacy if it's an argument for something. It's actually a criticism of your criticism. Oh hey, you tried to spin my comment with a different meaning. I guess you're guilty of an entirely different fallacy.
kjksf 16y ago
I don't really follow what in your example shows "gross mishandling of whitespace". The most popular languages are C, C++, Java and C# and Go's syntax is very similar to those. If anything, Python is the weird one in how it treats the whitespace and hence most likely to confuse people coming from other languages. As to optional semicolon elision - what is the problem with that? They make the code cleaner looking and gofmt will remove them for you even if you forget due to C/Java reflexes. I don't see the downside of making them optional.
- WalterBright 16y ago
  The problem is that the code looks correct for anyone coming from C, C++, Java, D, Javascript, etc., but produces unexpected results.
  - jibal 16y ago
    It's an interesting way to enforce K&R indentation style.
    - andralex 16y ago
      That statement takes considerable license with the word "interesting" and practically reverses the meaning of "enforce".
    - ponce 16y ago
      yay, every Allman indented program will silently fail
- andralex 16y ago
  Please make sure you give the example a close read, as it surprises even experienced Go programmers. Both examples look similar to code in the likes of C, C++, Java, and so on, _except_ the semantics gets radically changed depending on one line feed, which is very unlike those languages. I hope this clarifies things.
- deleted 16y ago
  [deleted]
- jibal 16y ago
  > I don't really follow what in your example shows "gross mishandling of whitespace". That truly speaks poorly of you. OTOH, the problem can easily be fixed by requiring a statement to contain at least one token.

stcredzero 16y ago

Name one language that doesn't have "a permanent trap for the unwary and a huge liability for people coming from other languages."

jibal 16y ago
tu quoque fallacy -- the worst possible form of argument FOR something.
- stcredzero 16y ago
  Only a fallacy if it's an argument for something. It's actually a criticism of your criticism. Oh hey, you tried to spin my comment with a different meaning. I guess you're guilty of an entirely different fallacy.

kjksf 16y ago

I don't really follow what in your example shows "gross mishandling of whitespace". The most popular languages are C, C++, Java and C# and Go's syntax is very similar to those. If anything, Python is the weird one in how it treats the whitespace and hence most likely to confuse people coming from other languages. As to optional semicolon elision - what is the problem with that? They make the code cleaner looking and gofmt will remove them for you even if you forget due to C/Java reflexes. I don't see the downside of making them optional.

WalterBright 16y ago
The problem is that the code looks correct for anyone coming from C, C++, Java, D, Javascript, etc., but produces unexpected results.
- jibal 16y ago
  It's an interesting way to enforce K&R indentation style.
  - andralex 16y ago
    That statement takes considerable license with the word "interesting" and practically reverses the meaning of "enforce".
  - ponce 16y ago
    yay, every Allman indented program will silently fail
andralex 16y ago
Please make sure you give the example a close read, as it surprises even experienced Go programmers. Both examples look similar to code in the likes of C, C++, Java, and so on, _except_ the semantics gets radically changed depending on one line feed, which is very unlike those languages. I hope this clarifies things.
deleted 16y ago
[deleted]
jibal 16y ago
> I don't really follow what in your example shows "gross mishandling of whitespace". That truly speaks poorly of you. OTOH, the problem can easily be fixed by requiring a statement to contain at least one token.