Re: scm_* API extension? [was] scm_* API question

[Rob Browning]

address@hidden writes:

>> For example, depending on what you're wanting to do, you might want to
>> allow different requests to be handled inside separate namespaces,
>> though they're all using a common set of code.  OTTOMH, I think you
>> could do this by putting the common functionality into a module, say
>> foo.scm, then doing something like this for *each* request:
>> 
>>   (use-modules (foo))
>>   (define foo-module (resolve-module '(foo)))
>> 
>>   ;; For each request...
>>   (define next-request-envt (make-safe-module))
>                           ^                ^
>                           |                |
>                         *----------------*
>                              |
>
>    Does this mean: module <=> environment in guile?

Hmm -- I suspect that depends on what we mean by each of those terms.
If it helps, in the above I just used envt loosely, I could have just
as easily used "-sandbox" as "-envt".

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD