Re:Just what does “code as data” mean anyway? (2014)
by Jtsummers on Friday February 16, 2018 @12:03PM
(#16393744)
Dylan. Dylan offered something like what you're asking for here. You had much the same power as traditionally structured lisps (it even has an alternative s-expression syntax).
Re:Just what does “code as data” mean anyway? (2014)
by kamaal on Friday February 16, 2018 @01:48PM
(#16394741)
You might want to take a look at Haskell. It comes from a family of languages called ML. And ML was known at one point as Lisp without parenthesis.
Modern incarnations of the same like F# are attractive too.
But Lisp is what it is, List processing.
> if the next line is indented, anything from the beginning of the current line starting at the indent till a dedent matching the current line indent is wrapped in one set of parentheses.
Seriously, what about this?
Now what about the DSL that now downright looks like slim-lang?: Or look at that: (even the qsort ones could be removed, but they balance [pivot] somehow)I'm perfectly happy with writing (+ 1 2 3) or whatever, the only parentheses that bother me are those that are perfectly delineated by indentation already, just as newlines perform the same duty as semicolons. They're just duplicated noise††.
† Other languages perform similar semicolon insertion, with varying degrees of success and ambiguities (JS==terrible, Go==terrific).
†† I know, you're supposed to get used to it and "unsee" them. I know, "paredit!". But seriously if you have to write a tool solely to produce noise, and you have to get accustomed to ignore said noise, well, somehow, something's off.