From: Jonathan Larmour <jifl@eCosCentric.com>
To: Jeff <jeff@kconline.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: very old getaddrinfo manpage
Date: Tue, 09 Jan 2007 04:18:00 -0000 [thread overview]
Message-ID: <45A31782.9070101@eCosCentric.com> (raw)
In-Reply-To: <20070109034435.GA55439@kconline.com>
Jeff wrote:
> A google search for "getaddrinfo example" showed
> http://ecos.sourceware.org/docs-2.0/ref/net-common-tcpip-manpages-getaddrinfo.html
> as the 4th item. In it the manpage is dated 1995 and claims that
> getaddrinfo is not thread-safe.
Actually it claims the implementation is not thread-safe, which is a bit
different. If someone thinks they're using the same implementation as a
random search result page, then that isn't good.
> I'm not familiar with Ecos in any way,
> shape, or form, but I'm curious: Are you really using such an old
> library? If not, the prevalence of this page in google is a real
> disservice to unsuspecting newcomers of socket programming and could use
> a bit of updating.
We can't help what google archives. Those are the docs associated with the
eCos 2.0 release, and so will not be changing. Although as it happens this
line is still in the docs, and the current getaddrinfo() is thread-safe,
so I will remove it.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
Company legal info, address and number: http://www.ecoscentric.com/legal
------["The best things in life aren't things."]------ Opinions==mine
prev parent reply other threads:[~2007-01-09 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 3:44 Jeff
2007-01-09 4:18 ` Jonathan Larmour [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45A31782.9070101@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=jeff@kconline.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).