Re: Eval, tail calls, (current-module), and backward compatibility

[Andy Wingo]

On Wed 18 Jan 2012 22:18, address@hidden (Ludovic Courtès) writes:

>         (('apply (f args))
>          (apply (eval f env) (eval args env)))

This is in primitive-eval (and here, `eval' is locally bound).  Mark is
talking about R5RS `eval' (`scm_eval').

> How does 1.8’s CEVAL behave?

CEVAL isn't relevant, because it's part of a lower level than `eval'.
1.8 also has this same problem with `eval'.

> It would be good to have test cases written against 1.8 that illustrate
> the behavior of (current-module) in different contexts.  Then we could
> see whether/how the same behavior can be achieved in 2.0.
>
> WDYT?

It's a good idea (for someone else to do ;-)))

Cheers,

Andy
-- 
http://wingolog.org/