From: Thorsten Kukuk <kukuk@suse.de>
To: "H.J. Lu" <hjl@lucon.org>
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: A getxxx_r version patch
Date: Sat, 10 Jul 1999 08:20:00 -0000 [thread overview]
Message-ID: <19990710172010.A10939@Wotan.suse.de> (raw)
In-Reply-To: <19990710151543.AC3C857B9@ocean.lucon.org>
On Sat, Jul 10, H.J. Lu wrote:
> >
> > Date: Fri, 9 Jul 1999 16:28:52 -0700 (PDT)
> > From: hjl@varesearch.com (H.J. Lu)
> >
> > Since we changed the return value of getxxx_r, I added a new version
> > for each function and kept the old one.
> >
> > I think you should also set errno since the new functions do not
> > necessarily do this. The whole point of having getXXbyYY_r returning
> > the error value is avoiding the use of thread-specific data.
> >
>
> I don't know what you mean. The new functions return "errno" in case
> of errors. Why do you want to set "errno" with "errno"?
The old functions sets errno and returns -1. But POSIX only says,
that the functions should return the errno value, and not setting errno.
So if the next functions or a later version will only return the errno
value, and doesn't set errno, your "old" functions will not longer work.
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE GmbH Deutschherrenstr. 15-19 90429 Nuernberg
Linux is like a Vorlon. It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.
next prev parent reply other threads:[~1999-07-10 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-09 16:28 H.J. Lu
1999-07-10 5:43 ` Mark Kettenis
1999-07-10 8:15 ` H.J. Lu
1999-07-10 8:20 ` Thorsten Kukuk [this message]
1999-07-10 8:28 ` H.J. Lu
1999-07-10 9:24 ` Ulrich Drepper
[not found] <19990709213944.B199E3FC1@varesearch.com>
1999-07-09 20:50 ` Ulrich Drepper
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=19990710172010.A10939@Wotan.suse.de \
--to=kukuk@suse.de \
--cc=hjl@lucon.org \
--cc=libc-hacker@sourceware.cygnus.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).