> Most importantly, we have added modules, allowing programmers to
> share portable libraries with ease. We hope implementors
> consider the effort of supporting the new standard small compared
> to that important benefit. Keep in mind that nothing is
> finalized yet, and at this stage we are see
Apologies if you receive multiple copies of this message.
The first draft of the R7RS small language standard is now
available at:
http://trac.sacrideo.us/wg/attachment/wiki/WikiStart/r7rs-draft-1.pdf
This is a relatively small revision to the R5RS, adding many of
the most frequently requested f
Hello all,
I just pushed some changes to the wip-peg branch. They eliminate the
last remaining circularity in the module imports and then add
everything to the Makefile. It passes all tests on my machine.
This is my first time pushing something, so I hope I did it correctly.
If the patches aren't
Hi Andy!
Thanks for your explanations.
Andy Wingo writes:
> On Wed 13 Apr 2011 23:34, l...@gnu.org (Ludovic Courtès) writes:
>
>> After reviewing f60a7648d5926555c7760364a6fbb7dc0cf60720 (which
>> addressed the same issue), I lean towards reverting it and instead
>> applying the patch I just se
Hi. Since the idea of creating something like CPAN is something folks
wants, I figure it would be good to collect as many thoughts and
information as possible in one place.
(I'd also appreciate links to relevant threads)
My thoughts, specifically, were for the client to be fairly similar in
funct
Hi Wolfgang,
On Mon 21 Mar 2011 01:24, Wolfgang J Moeller writes:
>> > (4) compiler: Now that compiling into hidden ~.cache/... directories
>> > has been declared the default behaviour, please cater to those
>> > (like me) who'd always look for their compiled files in the
>> > source
Hi Andreas,
On Thu 24 Mar 2011 01:47, Andreas Rottmann writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Could you send a patch to update the manual?
>>
> I have started working on this, but I'm notorious (at least to myself)
> for starving documentation-related work with interesting coding
Hi Ludovic,
On Wed 13 Apr 2011 23:34, l...@gnu.org (Ludovic Courtès) writes:
> After reviewing f60a7648d5926555c7760364a6fbb7dc0cf60720 (which
> addressed the same issue), I lean towards reverting it and instead
> applying the patch I just sent.
>
> The problem I see with f60a7648d5926555c7760364
