[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] compile-time eval-time mismatch
From: |
felix winkelmann |
Subject: |
Re: [Chicken-users] compile-time eval-time mismatch |
Date: |
Wed, 8 Dec 2004 18:55:29 +0100 |
On Wed, 8 Dec 2004 10:52:44 -0500, Michele Simionato
<address@hidden> wrote:
> For future reference of other people confused by eval-when:
>
>[...]
Thanks, Michele. That was indeed thorough.
>
> I would like to be sure instead that "eval" understands (at least) all
> r5rs constructs
> at all times.
>
The current version now supports `define-macro' in compiled code,
at run-time.
Note that `define-macro' is not R5RS. That was exactly the reason
why it wasn't available by default.
cheers,
felix
- Re: [Chicken-users] State machine using call/cc, (continued)
Re: [Chicken-users] compile-time eval-time mismatch, Michele Simionato, 2004/12/08
- Re: [Chicken-users] compile-time eval-time mismatch, felix winkelmann, 2004/12/08
- Re: [Chicken-users] compile-time eval-time mismatch, Michele Simionato, 2004/12/08
- Re: [Chicken-users] compile-time eval-time mismatch, felix winkelmann, 2004/12/08
- Re: [Chicken-users] compile-time eval-time mismatch, Michele Simionato, 2004/12/08
- Re: [Chicken-users] compile-time eval-time mismatch, Michele Simionato, 2004/12/08
- Re: [Chicken-users] compile-time eval-time mismatch,
felix winkelmann <=
Re: [Chicken-users] compile-time eval-time mismatch, felix winkelmann, 2004/12/08