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
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-de...@gnu.org.
Besides bug fixes, this release has a complete overhaul of the port
i
Héllo,
Yesterday someone on IRC asked for a new feature; the ability
to use xor/and/not/or to express queries. So here is it!
# Kesako?
The implementation is straight forward. Actually I defined
`xor*`, `and*`, `not*` and `or*` procedures that looks like
this:
```
(define* ((xor* a b) uid)
Andy Wingo :
> The trouble is that AFAIU there is no way to make non-blocking input
> work reliably with O_NONBLOCK file descriptors in the approach that
> Guile has always used.
>
> [...]
>
> The problem with this is not only spurious wakeups, as you note, but
> also buffering. Throwing an except
Hi,
I have a minimal LISP-1.5-resembling interpreter in C that now can
also interpret itself
https://gitlab.com/janneke/mes
It was inspired by the seemingly often ignored bootstrapping question
made so painfully visible by GuixSD and by OriansJ with their self
hosting hex assembler project.
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
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
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
On 2016-06-19 11:49, Amirouche Boubekki wrote:
```
(define* ((xor* a b) uid)
(if (procedure? a)
(if (procedure? b)
((xor* (a uid) (b uid)) uid)
((xor* (a uid) b) uid))
(if (procedure? b)
((xor* a (b uid)) uid)
(xor a b
```
That procedu
Héllo,
There is an implementation of guile parser combinators available here
[1].
Here's my attempt at explaining how it works:
http://hyperdev.fr/notes/getting-started-with-guile-parser-combinators.html
HTH!
[1] git clone git://dthompson.us/guile-parser-combinators
--
Amirouche ~ amz3
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
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
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
13 matches
Mail list logo
