Hello,
Attached...
I fixed the 2 tipos reported by Neil, thanks Neil.
Cheers,
David
From cb4fb3dd3386044fd063043629c77f16b2177227 Mon Sep 17 00:00:00 2001
From: David Pirotte
Date: Thu, 23 Jun 2016 16:59:33 -0300
Subject: [PATCH] Updating NEWS for 2.0.12 - draft
* NEWS: Updating NEWS for 2.0.1
Hi Neil,
> Nice work! I noted a couple of typos :
> - documention should be documentation
> - miss behaviour should be misbehaviour.
Thanks!
David
pgpa8DLURlUn4.pgp
Description: OpenPGP digital signature
On Thu 23 Jun 2016 18:57, Mark H Weaver writes:
> Andy Wingo writes:
>> Or, we could use print states. But print states are not so great and
>> ideally we would remove them eventually.
>
> We will need print states, or something like them, to support writing
> cyclic data structures as required
Andy Wingo writes:
> Or, we could use print states. But print states are not so great and
> ideally we would remove them eventually.
We will need print states, or something like them, to support writing
cyclic data structures as required by R7RS.
Mark
On Thu 23 Jun 2016 14:59, Daniel Llorens writes:
>>> We are pleased to announce GNU Guile release 2.1.3.
>>
>> Tried on my Mac OS 10.10.5 against Macports 2.3.4 w/ gcc-mp-5.
>> make check generated FAIL for test-language and test-stack-overflow and
>> stopped working after test-stack-overflow
>> On Jun 19, 2016, at 2:31 AM, Andy Wingo wrote:
>>
>> We are pleased to announce GNU Guile release 2.1.3.
>
> Tried on my Mac OS 10.10.5 against Macports 2.3.4 w/ gcc-mp-5.
> configure went OK
> make went OK
> make check generated FAIL for test-language and test-stack-overflow and
> stopp
On 23 June 2016 at 20:43, Andy Wingo wrote:
> On Thu 23 Jun 2016 11:24, Chris Vine writes:
>> Secondly, as I understand it in the end you want pre-emptive "green"
>> threads for guile, whereas my code equates to co-operative
>> multi-tasking, whilst also working with native threads. I must come
On Thu 23 Jun 2016 11:24, Chris Vine writes:
> A few things on that. First, there will always be a use for an event
> loop to do event-loopy things, irrespective of whether and how a
> coroutine interface is put around it. Sometimes you want to abstract
> things away, sometimes you don't.
Yep!
Chris Vine :
> First, there will always be a use for an event loop to do event-loopy
> things, irrespective of whether and how a coroutine interface is put
> around it. Sometimes you want to abstract things away, sometimes you
> don't.
Callback hell is my preferred programming paradigm. Any attem
On Thu, 23 Jun 2016 09:36:48 +0200
Andy Wingo wrote:
[snip]
> Excellent. Though I think that eventually we will want to bless one
> of these concurrency patterns as the default one, we're a long way
> away from that, and even if we do bless one I think we will always
> want to allow people to exp
Little typo:
On Thu 23 Jun 2016 09:36, Andy Wingo writes:
> The only drawback that I know of with the strategy of simply allowing
> users to use Guile's I/O primitives (e.g., `read-line') and assuming
> that they'll suspend when they block is that not all of the primitives
> that you would like
Nice work! I noted a couple of typos :
- documention should be documentation
- miss behaviour should be misbehaviour.
Neil
Original Message
From: David Pirotte
Sent: Wednesday, 22 June 2016 21:46
To: guile-devel
Subject: a draft for the top of the NEWS for 2.0.12
Heya,
Here below a d
On Thu 23 Jun 2016 00:44, Chris Vine writes:
> I have stirred myself and installed guile-2.1.3. On looking more at
> the suspendable ports code it became obvious and I haven't needed to
> adopt anything like ethreads with its "thread" abstraction: instead I
> have kept the approach already adopt
13 matches
Mail list logo
