chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too


From: Peter Bex
Subject: Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too
Date: Thu, 7 Nov 2013 11:10:42 +0100
User-agent: Mutt/1.4.2.3i

On Thu, Nov 07, 2013 at 10:09:24AM +0100, "Jörg F. Wittenberger" wrote:
> And sure one level up there was the broken letrec, which when written as 
> letrec* brings everything back to working order.

Ah, that's good to hear.

> Sorry for the noise again.
> 
> (Now I've got a different problem… rscheme is still supposed to run this 
> code. But I'm not inclined to add letrec* support to rscheme. :-/ )

The real problem is that your code wasn't portable to begin with.  It just
happened that both RScheme and CHICKEN had letrec* semantics for letrec.
The correct fix is to nest your letrecs or do some slight rewrite to get
rid of the implicit ordering requirement.

Perhaps a quick fix is to define letrec* as an alias for letrec when
running under RScheme, considering what it implements under the name
letrec really is letrec*.

Cheers,
Peter
-- 
http://www.more-magic.net



reply via email to

[Prev in Thread] Current Thread [Next in Thread]