From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org
Subject: Re: Code review for thread safeness
Date: Wed, 09 Mar 2005 15:48:56 +0100 [thread overview]
Message-ID: <lj7jkgswmf.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <6488947bc88c811e8e06efbdf810fe17@raeburn.org> (Ken Raeburn's message of "Mon, 7 Mar 2005 21:18:14 -0600")
Ken Raeburn <raeburn@raeburn.org> writes:
> If at all possible, this code should be switched to use get*by*_r, or
> in the gethostby* cases, perhaps getaddrinfo and getnameinfo.
Yes, definitely. Could you help with that?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-03-09 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 22:04 Code review for thread safeness Marius Vollmer
2005-03-07 22:36 ` Kevin Ryde
2005-03-08 1:18 ` Marius Vollmer
2005-03-08 3:18 ` Ken Raeburn
2005-03-09 14:48 ` Marius Vollmer [this message]
2005-03-09 16:23 ` Andreas Rottmann
2005-06-18 5:03 ` Ken Raeburn
2005-12-06 18:58 ` Marius Vollmer
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=lj7jkgswmf.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.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).