From: Andy Wingo <wingo@pobox.com>
To: Josep Portella Florit <jpf@primfilat.com>
Cc: guile-devel@gnu.org
Subject: Re: bug#15228: [PATCH] Close output port of I/O pipes
Date: Sat, 25 Jun 2016 17:49:50 +0200 [thread overview]
Message-ID: <8760sxb74x.fsf@pobox.com> (raw)
In-Reply-To: <628d9c7d-e7d5-6e55-1361-316629db8b4b@primfilat.com> (Josep Portella Florit's message of "Sat, 25 Jun 2016 15:51:18 +0200")
On Sat 25 Jun 2016 15:51, Josep Portella Florit <jpf@primfilat.com> writes:
>> I dunno how much we should push this "processes are a single port"
>> abstraction. In many ways for OPEN_BOTH pipes it's easier to deal with
>> an input and an output port and a PID instead of the pipe abstraction.
>> WDYT? We could just expose `open-process' from (ice-9 popen) to start
>> with. It would be good to allow other fd's or ports to map to the child
>> as well, e.g. stderr or any particular port; but I don't know what
>> interface we should expose.
>
> Since patching was inconvenient for me, I eventually used:
>
> (use-modules ((ice-9 popen) #:select (open-process)))
>
> Which works even though `open-process` is not exported.
Note that this behavior of #:select is a bug. We won't remove it in
stable-2.0 but we have removed it in master.
> For me, exporting `open-process` and documenting it would be enough.
Fine with me, many people have asked for this at this point. I guess
that's the next step for this bug.
> I also like the Racket interface to processes:
> <https://docs.racket-lang.org/reference/subprocess.html>
> (I've mostly used the `process` procedure.)
Duly noted! The more we steal from Racket, the better Guile will be :)
Andy
next prev parent reply other threads:[~2016-06-25 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-25 13:51 bug#15228: [PATCH] Close output port of I/O pipes Josep Portella Florit
2016-06-25 15:49 ` Andy Wingo [this message]
[not found] <1377937797.2030.5.camel@qwghlm>
2016-06-21 10:47 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760sxb74x.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=jpf@primfilat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).