From: Stanislav Ievlev <stanislav.ievlev@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: guile-1.8 question
Date: Thu, 15 Oct 2009 19:18:21 +0400 [thread overview]
Message-ID: <c5318fd90910150818p779cb058j86394b22ba9e753f@mail.gmail.com> (raw)
In-Reply-To: <m3y6ndt2io.fsf@pobox.com>
2009/10/15 Andy Wingo <wingo@pobox.com>:
> The ports C interface is rather crufty, as you have found :) Do you have
> any suggestions, or a patch? Keep in mind that we need to maintain
> backwards compatibility with these interfaces.
What do you think about documented additional function like this?
--
SCM
scm_c_fdopen(int fdes, const char* modes)
{
return scm_i_fdes_to_port (fdes, scm_mode_bits (modes), SCM_BOOL_F);
}
--
You can also use in libguile source files scm_i_fdes_to_port instead
of scm_i_fdes_to_port, and mark scm_fdes_to_port as a deprecated.
prev parent reply other threads:[~2009-10-15 15:18 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
2009-10-14 7:33 ` Stanislav Ievlev
2009-10-15 9:44 ` Andy Wingo
2009-10-15 15:18 ` Stanislav Ievlev [this message]
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=c5318fd90910150818p779cb058j86394b22ba9e753f@mail.gmail.com \
--to=stanislav.ievlev@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).