Hi Andy,
Andy Wingo writes:
> On Thu 10 Nov 2011 05:36, Mark H Weaver writes:
>> What method do you use to uniquify a macro-introduced top-level name,
>> such that a recompile yields the same name? I have doubts that this is
>> possible without breaking hygiene in some cases.
>
> See http://thr
Hi all,
> >> So what do you all think about:
> >>
> >> (define-module (foo)
> >> #:import ((bar)
> >> (only (baz) qux foo)
> >> ...))
> >>
> >> Or even:
> >>
> >> (define-module (foo)
> >> (import (bar)
> >> (only (baz) qux foo)
> >>
-[ Thu, Nov 10, 2011 at 12:16:38AM +0100, Andy Wingo ]
> > Indeed, it would probably need per-port mutexes, making I/O primitives
> > thread-safe by default, and perhaps providing unlocked variants like
> > libc does.
>
> I did this in master, but something was going wrong so I stubbed it out
On 10 Nov 2011, at 00:11, Andy Wingo wrote:
> On Thu 04 Aug 2011 10:56, Hans Aberg writes:
>
>> I try to understand how Guile transforms 'letrec' (returning to the
>> topic of an earlier post on this list).
>
> `letrec' is translated to various things, some of which are not Scheme.
> As Ludo n
Hi Mark,
On Thu 10 Nov 2011 05:36, Mark H Weaver writes:
> Hi Andy,
>
> What method do you use to uniquify a macro-introduced top-level name,
> such that a recompile yields the same name? I have doubts that this is
> possible without breaking hygiene in some cases.
See http://thread.gmane.org/
