{"id":121,"date":"2009-03-07T11:28:32","date_gmt":"2009-03-07T10:28:32","guid":{"rendered":"http:\/\/fiber-space.de\/wordpress\/?p=121"},"modified":"2009-03-09T06:23:01","modified_gmt":"2009-03-09T05:23:01","slug":"lonely-python-is-intelligent-design-and-how-to-liberate-from-it","status":"publish","type":"post","link":"http:\/\/fiber-space.de\/wordpress\/2009\/03\/07\/lonely-python-is-intelligent-design-and-how-to-liberate-from-it\/","title":{"rendered":"Lonely Python is Intelligent Design and how to liberate from it"},"content":{"rendered":"

Python is doomed. Well, of course it is not yet<\/em> doomed. Python is an evolutionary dead end living lonely on its own fitness plateau. It is clear that Python won’t have offspring because of significant whitespace aka indentation sensitivity. No children, no future.<\/p>\n

You might ask where are the news? There are none and we knew this for ever and a decade but sometimes it is in the news again. Read this post<\/a> by the author of a programming language called Reia. He struggles endlessly with indentation delimited blocks and finally abandons them for Ruby style `end` terminators ( not before a popularity poll in the Web 2.0 age and consulting the author of the failed Logix project who is now a Ruby advocate). Finally his language looks like Ruby which demonstrates the evolutionary fitness of Ruby. Python on the other hand is a piece of Intelligent Design<\/a>. Guido van Rossum has managed a ” beautiful set of compromises” when he designed the Python grammar. So it ends up in overspecialization whereas languages like JavaScript are flowing more with the nature. To illustrate this nature you might examine the file jQuery.js<\/a> that implements the popular jQuery library. The impatients might immediately scroll to the last line. It’s sweet.<\/p>\n

Some people have argued that Haskell style layouts<\/a> may save the soul of significant whitespace. Transplanted to Python this would imply mandatory explicit block delimiters that can also be omitted for the now classical indentation style. If you are not willing to decide just give multiple choice style freedom to anyone.<\/p>\n

In the rest of the article I’m discussing optional explicit delimiters for Python built into the grammar and making the statement\/expression distinction weightless. I promise not to cringe when it becomes “ugly”. Not behaving like little girls seems to be an evolutionary dead end among male, adult programmers as well but I take it with stoicism.<\/p>\n

Grammar Extension<\/em><\/p>\n

atom: ( '(' [embedded_stmt|yield_expr] ')' |'[' [listmaker] ']' |\r\n        '{' [dictmaker] '}' |\r\n         '`' testlist1 '`' |\r\n         NAME |  NUMBER | STRING+)\r\ntrailer: '(' [arglist|embedded_suite] ')' | '[' subscriptlist ']' | '.' NAME\r\n\r\nembedded_stmt: ( embedded_funcdef |\r\n    embedded_if_stmt |\r\n    embedded_while_stmt |\r\n    embedded_for_stmt |\r\n    embedded_try_stmt |\r\n    embedded_with_stmt |\r\n    embedded_classdef |\r\n    embedded_small )\r\n\r\nembedded_small: small_stmt (';' small_stmt)*\r\nembedded_suite: embedded_stmt+\r\nembedded_funcdef: [decorators] 'def' NAME parameters ':' embedded_suite\r\nembedded_if_stmt: ( 'if' test ':' embedded_suite ('elif' test ':' embedded_suite)*\r\n                   ['else' ':' embedded_suite])\r\nembedded_while_stmt: 'while' test ':' embedded_suite ['else' ':' embedded_suite]\r\nembedded_for_stmt: ( 'for' exprlist 'in' testlist ':' embedded_suite\r\n                     ['else' ':' embedded_suite] )\r\nembedded_try_stmt: ('try' ':' suite ((except_clause ':' embedded_suite)+\r\n                    ['else' ':' embedded_suite] ['finally' ':' embedded_suite] |\r\n                   'finally' ':' embedded_suite))\r\nembedded_with_stmt: 'with' test [ with_var ] ':' embedded_suite\r\nembedded_classdef: 'class' NAME ['(' [testlist] ')'] ':' embedded_suite<\/pre>\n
This is a conservative grammar extension of the official Python 2.5 Grammar<\/a>. Conservative means that all expressions \/ statements written in Python 2.5 remain valid. Those  non-terminals that substitute existing ones are `atom` and `trailer`. In detail the `testlist_gexp` non-terminal in `atom`  is replaced by the newly defined `embedded_stmt` non-terminal and instead of an `arglist` an `embedded_suite`can be used  . The `embedded_stmt` non-terminal is the gateway for all kinds of statements embedded into expressions. The statement-expression distinction becomes de facto obsolete.
\nWhat happens to significant whitespace? Post-processing the token stream filters whitespace inside of parentheses. Hence the token stream won’t contain `NEWLINE`, `INDENT`and `DEDENT` token within expressions. All those `embedded_xxx` non-terminals are only adjustments of existing ones reflecting the absence of the mentioned whitespace token in expressions. Notice that you can’t mix. Once you are living in a grammatical expression whitespace becomes definitely insignificant.<\/p>\n
The grammar is not LL(1) and you need a stronger parser than Pythons own one to handle it.  There is also no behavior associated with the new definitions. Semantics shall be entirely neglected and only the future shape of things shall be highlighted. Here are a few examples:<\/p>\n
Multiline Lambda<\/strong><\/p>\n
lambda x,y: (\r\n    z = x+y;              # semicolons always separate small statements\r\n    print z;\r\n    return z\r\n)(3, 2)<\/pre>\n
Long Assertions<\/strong><\/p>\n
assert ( if x>0:\r\n    x == 2\r\n    else:\r\n        x == -2)<\/pre>\n
The Return of the Return<\/strong><\/p>\n
def foo(x):\r\n    return ( return )<\/pre>\n
My Property
\n<\/strong><\/p>\n
x = property(\r\n    def fget(self):\r\n        return self._x\r\n    def fset(self, value):\r\n        self._x = value\r\n)<\/pre>\n
Function in the middle
\n<\/strong><\/p>\n
x + (def fact(n):\r\n     if n<=1:\r\n          return 1\r\n     else:\r\n          return fact(n-1))(7) + z<\/pre>\n","protected":false},"excerpt":{"rendered":"
Python is doomed. Well, of course it is not yet doomed. Python is an evolutionary dead end living lonely on its own fitness plateau. It is clear that Python won’t have offspring because of significant whitespace aka indentation sensitivity. No … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5,12,4],"tags":[],"_links":{"self":[{"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/posts\/121"}],"collection":[{"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/comments?post=121"}],"version-history":[{"count":27,"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/posts\/121\/revisions"}],"predecessor-version":[{"id":168,"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/posts\/121\/revisions\/168"}],"wp:attachment":[{"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/media?parent=121"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/categories?post=121"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/fiber-space.de\/wordpress\/wp-json\/wp\/v2\/tags?post=121"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}