[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Internal defines broken when compiled?
From: |
Felix |
Subject: |
Re: [Chicken-users] Internal defines broken when compiled? |
Date: |
Tue, 08 Feb 2011 09:47:57 +0100 (CET) |
From: Eric Jiang <address@hidden>
Subject: Re: [Chicken-users] Internal defines broken when compiled?
Date: Mon, 7 Feb 2011 14:10:21 -0500
> I was under the impression that internal defines expanded into
> letrec*, since csi runs and gives 4 for the sample (and using 'expand'
> was no help). Would it be reasonable, then, to request that csi have
> the same behavior and for csc to give a meaningful error when it
> detects this? (Or for internal defines to be letrec* a la R6RS?)
>
Internal defines expand into `letrec', but it has the same semantics
as R6RS `letrec*'. The compiler depends in a few places on the current
semantics, so I can't change the behaviour. A meaningful error would
of course be the right thing, but is a bit tricky to implement. I will
look into this.
cheers,
felix