From: Andy Wingo <wingo@pobox.com>
To: Stanislav Ievlev <stanislav.ievlev@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: guile-1.8 question
Date: Thu, 15 Oct 2009 11:44:31 +0200 [thread overview]
Message-ID: <m3y6ndt2io.fsf@pobox.com> (raw)
In-Reply-To: <c5318fd90910140033k1f313cddl79e76caff507e75@mail.gmail.com> (Stanislav Ievlev's message of "Wed, 14 Oct 2009 11:33:12 +0400")
On Wed 14 Oct 2009 09:33, Stanislav Ievlev <stanislav.ievlev@gmail.com> writes:
> 2009/10/14 Stanislav Ievlev <stanislav.ievlev@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).
> Ooops, I'm wrong.
> scm_fdes_to_port works is like "scm_C_fdopen", however function name
> is not good ;)
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.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-10-15 9:44 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 [this message]
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=m3y6ndt2io.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=stanislav.ievlev@gmail.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).