From: rixed@happyleptic.org
To: guile-user@gnu.org
Subject: Re: sharing a file descriptor with a port
Date: Sat, 18 Sep 2010 08:29:28 +0200 [thread overview]
Message-ID: <20100918062928.GB27074@yeeloong> (raw)
In-Reply-To: <87aang13se.fsf@ambire.localdomain>
-[ Fri, Sep 17, 2010 at 11:03:13PM +0200, Thien-Thi Nguyen ]----
> Perhaps you can make a port first; then use ???port->fdes???
> for file-descriptor based access; then close the port.
Wait a minute, you can close a port ?
... check check check ...
Ooooooookay. I might be blind somehow : Althoug I did see the fport_close()
function, I though it was only called by fport_free(). Of course
there is this nice scm_close_port function that calls it too, and
then destroys the port.
This is what I was after. Now I can close the file and destroy the port
too.
Thank you for the hint ! :)
Ashamedly yours,
next prev parent reply other threads:[~2010-09-18 6:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 9:30 sharing a file descriptor with a port Cedric Cellier
2010-09-17 21:03 ` Thien-Thi Nguyen
2010-09-18 6:29 ` rixed [this message]
2010-09-18 18:57 ` Thien-Thi Nguyen
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=20100918062928.GB27074@yeeloong \
--to=rixed@happyleptic.org \
--cc=guile-user@gnu.org \
/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).