elisp.js

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

Previously, previously, previously.

Tags: , , , , ,
Current Music: The Faint -- Machine in the Ghost ♬

10 Responses:

  1. shephi says:
    8 years ago at 2:50 pm

    closing all the dangling parens left in the wake of the emoticon infestation on the internet, one step at a time (:)
    • pete23 says:
      8 years ago at 3:02 pm

      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. flipping_hades says:
    8 years ago at 10:59 pm

    How long before someone gets the elisp-in-javascript and javascript-in-elisp implementations hooked up N levels deep?
    • lionsphil says:
      8 years ago at 10:57 am

      You're stuck in a time-loop. See the first "previously".
    • waider says:
      8 years ago at 11:31 am

      (error "Lisp nesting exceeds `max-lisp-eval-depth'")
      • flipping_hades says:
        8 years ago at 11:46 pm

        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:
          8 years ago at 10:50 am

          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:
    8 years ago at 8:17 pm

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

  • Previously