On Fri, Apr 15, 2016, at 23:46, Peter Ludemann via Python-Dev wrote: > If Python ever adopts the BCPL rule for implicit line continuation if > the last thing on a line is an operator (or if there's an open > parentheses), then the break-after-an-operator rule would be more > persuasive. ;) > > [IIRC, the BCPL rule was that there was an implicit continuation if > the grammar would not allow inserting a semicolon at the end of the > line, which covered both the open-parens and last-item-is-operator > cases, and probably a few others.] But I should shut up and leave shut > discussions to python-ideas. Sounds like Visual Basic. Meanwhile, Javascript's rule is that there's an implicit semicolon if and only if the grammar would not allow the two lines to be considered as a single statement. Insanity comes in all flavors.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4