On Wed 02 May 2012 23:15, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> Some versions of libgc do produce one SIGSEGV at startup, when
>> determining certain aspects of the process's memory layout. Just FYI :)
>
> Woow. :-) Do you know which versions/arches are affected?
I
Andy Wingo skribis:
> On Wed 02 May 2012 23:15, l...@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo skribis:
>>
>>> Some versions of libgc do produce one SIGSEGV at startup, when
>>> determining certain aspects of the process's memory layout. Just FYI :)
>>
>> Woow. :-) Do you know which v
Replying to myself, I've attached two more patches, which document two
more modules.
The approach I've been taking is to take the comments that modules
already have and convert them to the documentation format that
(texinfo reflection) understands. If people agree that this is a good
approach, the
Hello,
Thanks a lot for submitting them! Micro-commits are exactly what we want.
These patches raise an interesting issue. I do not use occam-channel,
and in fact I have no idea what it does since it has no documentation
and no tests. Normally I only reply to emails if I think I know
enough to g
Well, I think it's something like Actors but little different.
And I think it would be nice if there's a document for it.
On Fri, May 4, 2012 at 10:58 AM, Noah Lavine wrote:
> Hello,
>
> Thanks a lot for submitting them! Micro-commits are exactly what we want.
>
> These patches raise an interesti
