...
else if (c == "'") {
this.consumeChar();
value = ['list', [['symbol', 'quote']]];
value[1].push(this.parseExpression());
} ...
elisp.js
Indeed.
Tags: computers, lisp, mad science, perversions, religion, retrocomputing
Current Music: The Faint -- Machine in the Ghost ♬
10 Responses:
closing all the dangling parens left in the wake of the emoticon infestation on the internet, one step at a time (:)
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.
How long before someone gets the elisp-in-javascript and javascript-in-elisp implementations hooked up N levels deep?
You're stuck in a time-loop. See the first "previously".
I fail to see the what you're pointing out (yes, I've read that one too), unless you're trying to get an infinite comment regress going..
Never mind.
(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.
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).
Sorry, but I don't get it - what should that code bit show? That the implementation is slow?