Ok, as I mentioned previously, in Wings I'm defining a dynamic wings
environment to pass resources into request handlers.
Naturally, it's nice to use proper SRFI parameters where one can; the
environment is for things where they won't work elegantly, such as
structured names (data source "foo" h
"AS" == Alaric Snell-Pym <[EMAIL PROTECTED]> writes:
[...]
AS> He suggested I ask on The List, so here it is. Is there a way to
AS> write parameterize-from-alist without eval hackery, or shall I just
AS> use the wings dynamic environment?
'Course. However, I'd recommend for it to be im
On 10 Jul 2007, at 2:12 am, Ivan Shmakov wrote:
"AS" == Alaric Snell-Pym <[EMAIL PROTECTED]> writes:
[...]
AS> He suggested I ask on The List, so here it is. Is there a way to
AS> write parameterize-from-alist without eval hackery, or shall I
just
AS> use the wings dynamic environment?
Alaric Snell-Pym <[EMAIL PROTECTED]> writes:
AS> He suggested I ask on The List, so here it is. Is there a way to
AS> write parameterize-from-alist without eval hackery, or shall I just
AS> use the wings dynamic environment?
>> 'Course. However, I'd recommend for it to be implemented as a
>> f
On 16 Jul 2007, at 3:37 am, Ivan Shmakov wrote:
It's up to the caller to supply a correct alist to the
function.
E. g.:
Ah, but the original problem was that the alist was read from a file,
at run time!
ABS
--
Alaric Snell-Pym
Work: http://www.snell-systems.co.uk/
Play: http://
Alaric Snell-Pym <[EMAIL PROTECTED]> writes:
>> It's up to the caller to supply a correct alist to the function.
>> E. g.:
> Ah, but the original problem was that the alist was read from a file,
> at run time!
Well, symbols may either be simply `eval'ed, or ``mapped'' to
their re
