On Mon, Jan 2, 2017 at 7:40 AM, Edward K. Ream <[email protected]> wrote:
> They clutter code much like braces do.
My one potential objection to the code cluttering of braces, is that they
provide a completely non-assumed and guaranteed begin and end of a code
block.
I cannot explain how numerous my frustrations have been with "whitespace as
code" because this is human-illogical *('extra absence of text' should
literally mean mean 'nothing') and in my personal opinion (as I've not
studied parsers of code for C vs Python or YAML) harder to accurately
parse.
It also, I must say, is a steep learning curve for someone who is greatly
experienced with languages inclusive of braces (Bourne shell, C, a and
sadly PHP) and who has also been eternally confused by the syntax of BASIC
(it seemed harder than C or Pascal to me when I was starting to code in my
teens)...
YAML syntax for an Ansible Playbook style file took me multiple hours, and
finally coming across "the most insanely commented Playbook known to man"
on github: https://gist.github.com/marktheunissen/2979474
Yet I can look at a language that uses braces and intuitively know
precisely where code starts and stops, and know that indention and
whitespace is merely a style convention, and not actual syntax...
Mike
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
