Ouch, unbalanced curly brackets to end blocks? Maybe it's something like significant indentation (python) that will become natural once used. On first presentation though it sure seems scary.
I actually thought that was the neatest thing about this proposed language. I didn't get too excited about any of the design goals, but regarding syntax, this seems pretty original.
It allows for less syntax, which is a win for readability and also less boilerplate tokens, but still gives you a little freedom to mess with your indentation, unlike python. It means that (true) lambdas wouldn't be a syntactical enigma like they would be in python.
I don't think that you would need to use "}" to end a block though, since it looks like its missing the opening bracket, but maybe double semicolons would work, since they apparently aren't used elsewhere:
MAIN()
IO.write("Hello, World!\n")
;;
To be honest, the syntax that I have found to be nicest on the eyes so far has been Io:
`True lambdas' are overrated. The Python way is just fine. If you want to do anything that needs two lines, you are probably doing something complicated enough that this function deserves its own name.
The former is an error ("UnboundLocalError: local variable 'foo' referenced before assignment"), the latter is a workaround by manually boxing the variable in a list. I'm not sure why that works, but it's rather ugly.
The same, in Lua:
function acc(x)
local foo = x
return function()
foo = foo + 1
return foo
end
end
Oh, yes. You are mutating variables. You shouldn't do that anyway in a functional setting.
Python's syntax forces the language to guess whether you want to make a new variable or use the variable of the same name from the outer scope. The heuristic they have, says that if you assign something to the variable, you get a new one by default. You can declare
global x
before to assign to the variable in the outerscope.
I agree that the choice of "}" makes this seem weirder than it needs to. Something that doesn't "look" unbalanced would be better. What about "end" (like in Ruby but with no "begin")? It may be longer, but I actually find it easier/faster to type than a curly brace...
Probably what everyone said about python's indentation syntax.
I like both approaches. it's better then having useless {.
In some cases improve readability over python lack of marks.
and risking mod down by the audience we have here, it's (much (better then (the gratuitous use of (parenthesis in lisp)))))
Why do people use full tabs and put the braces at the indentation level of the opening statement? I have discovered the one true coding style: 2 spaces indent, opening character immediately after opening statement, closing character on new line indented with preceding code block
how (
is {
this();
}
any();
better(
than[$parenthesis]
);
);
A 2 space indent loses at 'visual overview' of larger (and more representative) expanses of code. A 4 space indent maintains clarity at the level of a skim or casual glance, even if it "fails" at the contrived (but simple) example shown here.
Supporting "larger" expanses of code is a pathological feature, not a benefit. If the code doesn't break back to the baseline after more than half a page, there's something wrong with that code in 99.9% of the cases.
Though true, a 2 space indent visually 'breaks' whenever there's (conservatively speaking) more than 8 lines of code on a single level followed by several further indented lines. After that, the indentation level of the immediately following less indented lines is not available to the average skimmer.
