2009/3/8 Tim Roberts :
> Tim Rowe wrote:
>>
>>I don't think the article is right that "it's silly to have some
>>expression/statement groupings indentation based and some grouped by
>>enclosing tokens" -- provided it's done right. The OCAML-based
>>language F# accepts OCAML enclosing tokens, but i
On Tue, Mar 10, 2009 at 12:39 PM, wrote:
>
>
> John> The only complaint I have there is that mixing tabs and spaces for
> John> indentation should be detected and treated as a syntax error.
>
> Guido's time machine strikes again (fixed in Python 3.x):
>
> % python3.0 ~/tmp/mixed.py
>
John> The only complaint I have there is that mixing tabs and spaces for
John> indentation should be detected and treated as a syntax error.
Guido's time machine strikes again (fixed in Python 3.x):
% python3.0 ~/tmp/mixed.py
File "/home/titan/skipm/tmp/mixed.py", line 3
Kay Schluehr wrote:
On 6 Mrz., 02:53, bearophileh...@lycos.com wrote:
This is an interesting post, it shows me that fitness plateau where
design of Python syntax lives is really small, you can't design
something just similar:
http://unlimitednovelty.com/2009/03/indentation-sensitivity-post-mort
Tim Rowe wrote:
>
>I don't think the article is right that "it's silly to have some
>expression/statement groupings indentation based and some grouped by
>enclosing tokens" -- provided it's done right. The OCAML-based
>language F# accepts OCAML enclosing tokens, but if you mark the groups
>with in
On 6 Mrz., 02:53, bearophileh...@lycos.com wrote:
> This is an interesting post, it shows me that fitness plateau where
> design of Python syntax lives is really small, you can't design
> something just similar:
>
> http://unlimitednovelty.com/2009/03/indentation-sensitivity-post-mort...
>
> Living
2009/3/6 :
> This is an interesting post, it shows me that fitness plateau where
> design of Python syntax lives is really small, you can't design
> something just similar:
>
> http://unlimitednovelty.com/2009/03/indentation-sensitivity-post-mortem.html
I don't think the article is right that "it
Steven D'Aprano wrote:
You can have one, or the other, but not both, unless you're willing
to have a "practicality beats purity" trade-off and create a second way of
grouping blocks,
I propose /* and */ as block delimiters.
There, you have auto-documenting code, ahah!
--
http://mail.python.o
On 6 Mrz., 02:53, bearophileh...@lycos.com wrote:
> This is an interesting post, it shows me that fitness plateau where
> design of Python syntax lives is really small, you can't design
> something just similar:
>
> http://unlimitednovelty.com/2009/03/indentation-sensitivity-post-mort...
>
> Living
bearophileh...@lycos.com writes:
> Indentation-wise Haskell syntax seems one of the very few local maxima
> that is close enough to the little fitness plateau where Python is.
It is odd, the article claims indentation-aware syntax only works
in languages that separate statement and expressions, bu
bearophileh...@lycos.com wrote:
Living on a small fitness plateau isn't good, even if it's very high,
because it's evolutionary unstable :-(
Actually I think, in biological sense speaking [citation needed], if one
path has an advantage over the other path, even if the other path is in
majori
bearophileh...@lycos.com wrote:
> This is an interesting post, it shows me that fitness plateau where
> design of Python syntax lives is really small, you can't design
> something just similar:
>
>
http://unlimitednovelty.com/2009/03/indentation-sensitivity-post-mortem.html
>
> Living on a small
This is an interesting post, it shows me that fitness plateau where
design of Python syntax lives is really small, you can't design
something just similar:
http://unlimitednovelty.com/2009/03/indentation-sensitivity-post-mortem.html
Living on a small fitness plateau isn't good, even if it's very
13 matches
Mail list logo
