if z:
print 'a'
print 'b'Sure, when you paste code somewhere that expects prose (Facebook status updates, for example), it will consolidate consecutive whitespace and thereby remove the indentation, but you shouldn't be pasting code into a place like that anyway, because no matter what you do it'll be unreadable, and most people aren't going to be interested enough to put it into their editor to autoformat.
But the OP's point is that you can't know how many lines make up the indented block, since there is no explicit block-end-marker left if the indent is gone.
Except if you have, for example, an if statement. if x: y() is valid.
The main problem with indent oriented languages is that not everyone is or wants to use a modern editor. Then there are LISPers who think braces everywhere are a swell idea.
Nonsense.
Try pasting a block of Python into Hacker News and you get something that starts off like this:
import os import random def do_something(x): if x: fd = os.open(x)
and only gets worse. A language with braces/semicolons has no such problem; it is easier to communicate with others, and the absolute value of being able to communicate with others when starting a new language is exceptional.
If someone posts more than two lines of practically any curly-brace language as one line, it's illegible. Yes, you can pull it into an editor and fix it automatically, but it's a huge waste of time that is best fixed by simply posting the code properly in the first place.
You might not be able to read it, but others can, so it is by definition not illegible.
"Indention language", on the other hand, has actually lost its meaning and therefore is illegible.
> it's a huge waste of time that is best fixed by simply posting the code properly in the first place
Helping others is never a waste of time, but telling people thy are too stupid to ask for help correctly is cruel.
Asking others politely to help you help them is not cruel in any way. If you allow a community to become a place where people can ask questions without putting any effort at all in themselves, you end up with all the people who can actually help leaving, and your community being full of people who will only ever put in the bare minimum of effort.
So you could read and debug a 5000-line program written all on one line without reformatting it?
If it fits on a page I don't have trouble reading it. Line breaks tend to make it harder to fit on a page and not easier.
Example:
In fact I think it would make it worse.
This has come up before, if you're interested:
* https://news.ycombinator.com/item?id=8476189
* https://news.ycombinator.com/item?id=8476702
It is also something I set out to learn how to do because I saw someone else do it: If someone produces smaller and faster code than me, then I should want to learn from it.
When working with others, I will often extemporise my code for their sake. I sometimes make mistakes when doing this, but sometimes making friends is more important than fast and correct programs.
illegible, adjective: not clear enough to read.
Says nothing about "others being able to read". A doctor's handwriting can be illegible to everyone but the doctor, and not be a contradiction to the definition of illegible.
> Helping others is never a waste of time
If someone cares so little as to paste unformatted code on a forum which provides simple tools to display formatted code, how much value can you really put in their ability to provide quality code? How is requiring someone else decipher something you didn't care enough to post correctly not ultimately a waste of everyone's time?
Well, I know it may sound a little bit awkward, but sometimes I just want it to see it work before looking into it, and copy-pasting curly-braced kind of code is perfect for that. So the curly-braced style solves a lot of such inside content distortions and actually frees me from a huge waste of time.
import os
import random
def do_something(x):
if x:
fd = os.open(x)
Note2: If one line with two spaces is too long, it will mess the whole thread, so if you ever want to quote use italics instead of spaces.]PEPpy Python should have four spaces at each level of indentation...not two.
Now I feel better
You're talking about a web site that seems to have been written by web developers who don't know Javascript exists.
Any Python parser will be able to format your snippet correctly.
If I were designing a language, its compatibility with naive commenting systems (or catering to users who refuse to use code blocks provided by most modern commenting systems) would be pretty low on my list.
Whitespace, even disregarding indentation, is already very significant to a number of modern languages. Why, then, is this particular form of significance bad?
You are arguing that braces should be kept so people who don't indent their code properly on HN can be understood.
import os
import random
def do_something(x):
if x:
fd = os.open(x)I wonder how a comment system that made downvotes public would do. And further, if the downvoter was required to give a one line justification. And further yet, if the downvote itself could be downvoted.
Oh, scrap all that. I'd like to see would happen if downvotes were eliminated entirely, so things sorted to the top purely by upvotes.
White space has significance for humans. The road to the Turing tarpit is paved with human intentions. Describing computation mathematically is a solved problem. Expressing it clearly for and by humans, not so much.
Haskell is particularly guilty of creating several different indenting possibilities, and does require constant intervention. Python is less bad, but still requires more effort than C for example.
[0] https://www.haskell.org/onlinereport/syntax-iso.html#sect9.3
Case in point: putting if _ then _ else on separate lines is fine, but inside a do-notation it causes problems because the layout stage inserts semicolons between the parts, and the production rules listed at the bottom of the page do not include optional semicolons in the "if" alternation. You need to indent the then/else to overcome it. This problem is fixed with a hack[0], which fortunately has no side-effects for the rest of the language, but it just shows that throwing together ad-hoc rules for parsing code, rather than well understood theory like LR parsing, is inviting room for problems.
With CFG subsets like LR/LL, every production rule in these grammars is also a valid LR/LL grammar - in other words, it's not only the entire grammar of a language that is context-free, but all the parts are too. An indentation-sensitive language is only context-free when looked at for the entire language grammar, but the individual production rules of are context-sensitive. You can't just copy and paste some code into the syntax without providing this context (by means of manually indenting the code).
[0]:https://ghc.haskell.org/trac/haskell-prime/wiki/DoAndIfThenE...
Anyway, Haskell is a very instructive example about how semantic indentation creates problems.
> Haskell is particularly guilty of creating several different indenting possibilities, and does require constant intervention
with:
> You really have to design your language around it for it to work well. Haskell has a a lot of syntactic craziness in the name of simplicity.
Where "it" would seemingly be indentation, implying Haskell wasn't designed around making indentation simple.
Any problems in parsing are typically only encountered by stateless parsers.
https://github.com/djc/runa/blob/master/runac/parser.py#L54
(Runa uses tabs for indentation, not spaces, but it's basically the same thing.) Whitespace at the start of a line is a separate token, then I add a thin layer of processing that turns a change of indentation level (i.e. count chars in the token contents) into INDENT or DEDENT tokens.
What? My editor indents stuff for me as per PEP8. I don't have to think about it. Why do you?
def fun():
for x in xs:
if a:
b
c
There's no way for an editor to know where to re-indent c to. You have to cycle through the indents manually.So, you're at `b`, you hit enter: next line, same indent level. Now you hit backspace: indent level matches `if`. Again: indent level matches `for`. Type c, there it is.
If you had curly braces, you'd use } instead of backspace. Literally the same number of keystrokes, no?
Or were you talking about something else and did I misunderstand?
No, I use braces for the computer, and the computer automatically and unambiguously indents it for me.
If anything the wasted effort happens in whitespace significant languages like Haskell and Python where the computer can't tell what you want and you have to cycle through all sensible indentations (for every line!)