Comment Re:Many languages and... (Score 1) 729
Two reasons not to do that. First, "2." in at least some of those is a floating-point 2, so "i = 2." by itself would be ambiguous: does this assign an integer 2 and end the statement, or assign a floating-point 2. (and writing 2.0 doesn't really clarify, but rather raises the question of whether the 0 starts another statement). Second, all the old COBOL programmers who escaped that ecosystem would have something like anti-LSD-style flashbacks, and that can be dangerous.
That's still workable. A period followed by an end of line, or whitespace is the end of statement. A period that's between two numbers is a floating point number. A period surrounded by non-numbers and non-whitespace is a compilation error. I realize that the ship might have sailed as far as this is concerned, but if done originally I think it would have helped a lot of people ramp up on how to code.