From: Stanislav Ievlev <stanislav.ievlev@gmail.com>
To: guile-devel@gnu.org
Subject: Re: guile-1.8 question
Date: Wed, 14 Oct 2009 11:05:03 +0400 [thread overview]
Message-ID: <c5318fd90910140005y285b1e88o169b876ff3ca7fcf@mail.gmail.com> (raw)
In-Reply-To: <c5318fd90910140002u672739adi7e3657552891e9ec@mail.gmail.com>
As I understand you should mark scm_fdes_to_port as a deprecated and
don't use it in own code (e.g. in socket.c).
2009/10/14 Stanislav Ievlev <stanislav.ievlev@gmail.com>:
> Greetings!
>
> There are several functions exists to convert file descriptor into guile port:
> * scm_fdes_to_ports - search for fdes in already opened ports
> * scm_fdes_to_port - looks like internal function, not documented, but
> exists in header files.
> * scm_fdopen - looks like public function.
>
> What is the difference between scm_fdes_to_port and scm_fdopen? What
> function should I use?
>
> Have you any plans to made this API simpler?
>
> --
> With best regards
> Stanislav Ievlev.
>
next prev parent reply other threads:[~2009-10-14 7:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 7:02 guile-1.8 question Stanislav Ievlev
2009-10-14 7:05 ` Stanislav Ievlev [this message]
2009-10-14 7:33 ` Stanislav Ievlev
2009-10-15 9:44 ` Andy Wingo
2009-10-15 15:18 ` Stanislav Ievlev
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=c5318fd90910140005y285b1e88o169b876ff3ca7fcf@mail.gmail.com \
--to=stanislav.ievlev@gmail.com \
--cc=guile-devel@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).