From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] nonblocking write/recv/send/connect/accept
Date: 29 Jun 2002 13:50:16 +0200 [thread overview]
Message-ID: <87sn36gv7r.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20020628200733.A3168@kiwi.pyrotechnics.com>
Christopher Cramer <crayc@pyro.net> writes:
> On Sat, Jun 01, 2002 at 05:58:29PM +0200, Marius Vollmer wrote:
> > Could you try to collect this pattern into its own set of functions
> > (ala fport_wait_for_input)? I think this will make the code much
> > cleaner.
>
> One thing is, we need functions in both socket.c and fports.c, and
> fport_wait_for_input is static. Should I put the functions in both files,
> or make them extern?
The point is to collect similar code, so I'd say we should have only
one copy of a function. Also, there might be more opportunities to
use it in the future. A good place to put it would be iselect.c, I
think.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-06-29 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 19:03 [PATCH] nonblocking write/recv/send/connect/accept Christopher Cramer
2002-05-22 13:20 ` Marius Vollmer
2002-06-01 15:58 ` Marius Vollmer
2002-06-29 1:07 ` Christopher Cramer
2002-06-29 11:50 ` Marius Vollmer [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=87sn36gv7r.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).