On Wed, Aug 08, 2007 at 05:54:04AM +0100, Tony Sidaway wrote:
My current approach is to compile the user script with an included
preamble which redefines important stuff. For instance:
(define-macro (dummy name)
`(define ,name (lambda x (force (delay (begin (display (format ~a
is not
Ivan Raikov scripsit:
Pyffi uses the Python C interface to convert Python values to Scheme
values and vice versa, and to invoke Python procedures and methods,
and automatically convert their arguments and return values to and
from Python and Scheme representations. It supports Python numeric
On 8/8/07, Tony Sidaway [EMAIL PROTECTED] wrote:
And so on.
It seems to me that I need to do this otherwise just about everything
in the namespace will be available at runtime, co-optable for bad
stuff.
Or am I just being a silly sausage? Is there a better way of doing this?
The sandbox
Hello.
I've been having some problems getting the sqlite3:for-each-row
procedure from the sqlite3 egg to play along nicely with the
iterator-stream procedure from the stream-ext egg.
The iterator-stream procedure uses continuations to turn an iteration
inside out: to build a lazy (srfi-40)
