Andy Wingo wrote:
1) As you suggested, try doing some parts of this with new VM
operations. Like all of these in one op, or maybe just a "reference and
error on void" as one op, and/or "lookup the variable in some module,
and create it if not there" as another. I think we need some planning
to
On Wed 15 Jul 2009 10:36, Daniel Kraft writes:
> Ludovic Courtès wrote:
>>> as well as found a (hopefully good) solution to automatically create
>>> fluids not yet present on reference.
>>
>> Is each Elisp variable mapped to a fluid? Eventually, you may need VM
>> instructions for fluid-{ref,se
Hello!
On Tue 14 Jul 2009 21:48, Daniel Kraft writes:
> (defun primep (p &optional from)
> (let ((i (if from from 2)))
> (while (and (/= (% p i) 0) (<= (* i i) p))
> (setq i (1+ i)))
> (/= (% p i) 0)))
>
> (primep 1283939) -> #t
This is fantastic.
> While of course the #f shoul
Ludovic Courtès wrote:
as well as found a (hopefully good) solution to automatically create
fluids not yet present on reference.
Is each Elisp variable mapped to a fluid? Eventually, you may need VM
instructions for fluid-{ref,set!}, to speed things up.
Yes it is; and I agree that variable
Hi Daniel!
Daniel Kraft writes:
> yesterday and today I implemented lambda expressions and
> defvar/defconst/defun for elisp
Great news!
> as well as found a (hopefully good) solution to automatically create
> fluids not yet present on reference.
Is each Elisp variable mapped to a fluid? Ev
