On 2015-11-07 20:22, Mathieu Lirzin wrote:
Hi,
Since the “libraries” page in the website will probably change
regularly
it is useful to have some abstractions to facilitate the maintenance.
A second step would be to provide a way to sync the software entries
with Guix package definitions.
--
Hi,
Since the “libraries” page in the website will probably change regularly
it is useful to have some abstractions to facilitate the maintenance.
A second step would be to provide a way to sync the software entries
with Guix package definitions.
--
Mathieu Lirzin
>From 7ad1e1bd620d48099013b276
Artyom Poptsov writes:
> Oh sorry, there was a mistake in my previous mail. 'scm_i_fdes_to_port'
> is an internal procedure, but 'scm_fdes_to_port' is defined as Guile API
> and should be available to Guile programs. Here's its definition:
>
> SCM
> scm_fdes_to_port (int fdes, char *mode, SCM n
Oh sorry, there was a mistake in my previous mail. 'scm_i_fdes_to_port'
is an internal procedure, but 'scm_fdes_to_port' is defined as Guile API
and should be available to Guile programs. Here's its definition:
--8<---cut here---start->8---
SCM
scm_fdes_to_por
Hello Jan,
do you need to read the data from the file descriptor in a Scheme
program? If so, I guess you can make a wrapper procedure [1] that uses
'scm_fdes_to_port' from 'libguile.h' to convert your file descriptor to
a SCM port and return the port into the Scheme world.
Here's the description
Hello Guilers,
how do I read data from a file descriptor? I already have an fd required
from elsewhere that I need to read data from and actually have no idea how
to do that. I read through the documentation on ports, but that didn't
help. The fd actually points to a socket.
In C, I have somethin