On Feb 15, 9:48 pm, Chris Page <usenet@[EMAIL PROTECTED]
> wrote:
> In article <533m7jF1k5o9...@[EMAIL PROTECTED]
>,
> Andreas Bogk <andr...@[EMAIL PROTECTED]
> wrote:
>
> > The current Dylan syntax consumes a lot of vertical space due to the
> > "end" statements, I don't like that.
>
> I'd love to see Dylan changed to make end statements optional to sup****t
> a syntax more like Python's.
>
> As far as I am aware it is an objective fact of typography that "end",
> ")" and "}" all add visual noise and are unnecessary for humans to
> correctly read and write code when line breaks and indenting are
> available. For historical reasons, most popular languages ignore
> whitespace and require explicit tokens to end scopes, but humans do not
> require this solution.
I'll second that. I love Dylan, but there does seem to be quite a bit
of unnecessary verbosity in it. F# (an OCaml dialect for .NET) and
Nemerle (another functional language for .NET) have added optional
whitespace significant syntax that I have found aids in readability.
But I don't see that as a priority. I would put a working debugger on
Unix and a gtk+ backend at the top of my list.
|
