elisp.js

Indeed.
...
else if (c == "'") {
  this.consumeChar();
  value = ['list', [['symbol', 'quote']]];
  value[1].push(this.parseExpression());
}
...

Previously, previously, previously.

Tags: , , , , ,

10 Responses:

  1. shephi says:

    closing all the dangling parens left in the wake of the emoticon infestation on the internet, one step at a time (:)

    • pete23 says:

      surely you need to retroactively open them? and by need, i mean... ach...

      this is one of those things which establishes perpetual motion in the rightwrongometer.

  2. How long before someone gets the elisp-in-javascript and javascript-in-elisp implementations hooked up N levels deep?

    • lionsphil says:

      You're stuck in a time-loop. See the first "previously".

    • waider says:

      (error "Lisp nesting exceeds `max-lisp-eval-depth'")

      • pshaw. That limit's gotta be a constant somewhere in emacs. We have 64-bit addressing now - we should be able to nest them at least a couple of dozen deep.

        • kehoea says:

          It's a variable, called, startlingly enough, `max-lisp-eval-depth'. With

          (let ((max-lisp-eval-depth most-positive-fixnum))
          ...)

          I get a core dump at 162081 recursive calls on this 64-bit machine; it's a lot sooner if the recursive function makes any binding (most relevantly, if it takes any arguments; for the non-Emacs-Lisp people, let me draw your attention to the fact that dynamic scope sucks).

  3. anktastic says:

    Sorry, but I don't get it - what should that code bit show? That the implementation is slow?