chicken-hackers
[Top][All Lists]
Advanced

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

Re: [Chicken-hackers] [PATCH] Fix #1133


From: Felix Winkelmann
Subject: Re: [Chicken-hackers] [PATCH] Fix #1133
Date: Mon, 30 Jun 2014 12:58:46 +0200 (CEST)

From: Evan Hanson <address@hidden>
Subject: Re: [Chicken-hackers] [PATCH] Fix #1133
Date: Thu, 26 Jun 2014 11:49:01 -0700

> On 2014-06-26 16:29, Peter Bex wrote:
>> > BTW, what's the status of that egg? The last time I looked it seemed
>> > to be basically complete. Or is there still anything missing? (I know
>> > there are some rough edges, and obscure warnings, but does it
>> > basically work?)
>> 
>> I've asked Seth and he said it's working adequately.  Maybe Evan can
>> provide us with some more in-depth info.
> 
> There's not much that's obviously missing anymore, it's mostly rough
> edges as you said. The list at https://wiki.call-cc.org/r7rs-tasks#todo
> is up to date.
> 
> Actually, the most important todo is probably documentation of the
> gotchas/limitations/interplay between the egg and core that aren't
> obvious from that list, e.g. `(import (foo bar))` doesn't load code
> from ./foo/bar.scm (or ".sld" as seems to have become common), one must
> `(import-for-syntax (r7rs))` to get R7RS's syntax-rules, and so on. But,
> overall, I'd be fine with releasing it with such disclaimers just so
> people can start hacking at it.

Excellent! Evan, would you mind writing a wiki-page for the egg?
Perhaps based on the r7rs-tasks page?

I can try to figure out something for the import-for-syntax.

The thing about "define-values" is related to not being able to handle
extended (DSSSL) lambda-lists, is that correct?  If yes, we can
probably ignore that for the time being.

Oh, and thanks very much for putting so much effort into the r7rs egg.
Well done, indeed! 

I will try to give it some testing and perhaps I can fix a few open
issues.


felix



reply via email to

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