Re: anyone define port types?

2016-06-19 Thread Chris Vine
On Mon, 20 Jun 2016 13:38:39 +1000 William ML Leslie wrote: > On 20 June 2016 at 06:09, Chris Vine > wrote: > > OK I am grateful for your patience in explaining this. I need to > > think about it, but while this works where all events come from > > user-derived events, I doubt that this would wo

Re: anyone define port types?

2016-06-19 Thread William ML Leslie
On 20 June 2016 at 06:09, Chris Vine wrote: > OK I am grateful for your patience in explaining this. I need to think > about it, but while this works where all events come from user-derived > events, I doubt that this would work with guile-gnome and the glib main > loop in the round, because for

Re: anyone define port types?

2016-06-19 Thread Chris Vine
On Sun, 19 Jun 2016 19:48:03 +0200 Andy Wingo wrote: > On Sun 19 Jun 2016 17:33, Chris Vine > writes: > > > The answer I have adopted when reading from TCP sockets is to > > extract individual bytes only from the port into a bytevector using > > R6RS's get-u8 procedure and (if the port is textua

Re: anyone define port types?

2016-06-19 Thread Andy Wingo
On Sun 19 Jun 2016 17:33, Chris Vine writes: > The answer I have adopted when reading from TCP sockets is to extract > individual bytes only from the port into a bytevector using R6RS's > get-u8 procedure and (if the port is textual rather than binary) to > reconstruct characters from that using

Re: [PATCH 2/2] Add reference to the lack of "non-greedy" variants

2016-06-19 Thread Andy Wingo
Oh my goodness Diogo, this patch and the one before were applied by no one :( Our bad. I just applied them, as they are small. In the future please nag over IRC, and if you have bigger patches please let's start the copyright assignment process; find me on IRC to get that done. We'll try to do b

Re: proposal: deprecate dynamic states

2016-06-19 Thread Andy Wingo
Hi :) It took more than a couple days, ahem, but let's do this. Just a heads-up. Andy On Sun 09 Mar 2014 18:33, Andy Wingo writes: > Hi, > > The manual claims that you can use fluids as thread-local variables, but > that's not really true -- we expose this strange "dynamic state" > interface

Re: anyone define port types?

2016-06-19 Thread Chris Vine
On Sun, 19 Jun 2016 11:13:17 +0200 Andy Wingo wrote: > Hi :) > > On Sun 12 Jun 2016 10:25, Chris Vine > writes: > > >> > >> http://www.gnu.org/software/guile/docs/master/guile.html/Input-and-Output.html > >> > > > > The documentation indicates that with the C ports implementation in > > g

Re: anyone define port types?

2016-06-19 Thread Andy Wingo
Hi, You are arguing for new I/O primitives with different semantics, and that's fine and good :) My goal was to add the ability to sensibly work with non-blocking ports using Guile's existing primitives, especially the textual ones. This effort was started because of the ethreads work I did abou

GNU Guile 2.1.3 released [beta]

2016-06-19 Thread Andy Wingo
We are pleased to announce GNU Guile release 2.1.3. Guile 2.1.3 is the third pre-release in what will eventually become the 2.2 release series. We encourage you to test this release and provide feedback to guile-devel@gnu.org. Besides bug fixes, this release has a complete overhaul of the port i

Re: anyone define port types?

2016-06-19 Thread Andy Wingo
Hi :) On Sun 12 Jun 2016 10:25, Chris Vine writes: >> >> http://www.gnu.org/software/guile/docs/master/guile.html/Input-and-Output.html > > The documentation indicates that with the C ports implementation in > guile-2.2, reads will block on non-blocking file descriptors. Correct. > This wil