Live data from Hacker News

(How to Write a (Lisp) Interpreter (In Python)) (2010)

norvig.com

11–20 of 73 posts

Re: (How to Write a (Lisp) Interpreter (In Python)) (2010)

#11

Earlier quoted context omitted.

First day of paradigms course in the 2000s and prof says "if your opinion of Scheme is too many parentheses, then you're an idiot." Needless to say that was my opinion and every day I think, more and more, how right he was. (later I did make some gui apps that included scripting and chose s-expr syntax because of how simple it is to implement it)

main problem isn't brackets themselves - it's that they're too on the right had brackets been displayed as curly braces in C - everything would look much more manageable

so, instead of

    (foo (bar (1 2 3))
you'd prefer

    {
      foo {
        bar {
          1
          2
          3
        }
      }
    }
is that right?

Re: (How to Write a (Lisp) Interpreter (In Python)) (2010)

#13

Earlier quoted context omitted.

First day of paradigms course in the 2000s and prof says "if your opinion of Scheme is too many parentheses, then you're an idiot." Needless to say that was my opinion and every day I think, more and more, how right he was. (later I did make some gui apps that included scripting and chose s-expr syntax because of how simple it is to implement it)

main problem isn't brackets themselves - it's that they're too on the right had brackets been displayed as curly braces in C - everything would look much more manageable

I changed my opinion about parens when I stopped formatting like C, and used indent rather than parens to denote blocks. That is, a large amount of them at the end is totally fine.

Re: (How to Write a (Lisp) Interpreter (In Python)) (2010)

#18
post #11

Earlier quoted context omitted.

main problem isn't brackets themselves - it's that they're too on the right had brackets been displayed as curly braces in C - everything would look much more manageable

so, instead of (foo (bar (1 2 3)) you'd prefer { foo { bar { 1 2 3 } } } is that right?

Emacs vs vim, go!
Post reply on HN