From: Heikki Orsila <shdl@zakalwe.fi>
To: Ulrich Drepper <drepper@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
mtk.manpages@gmail.com, Al Viro <viro@zeniv.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: dup2() vs dup3() inconsistency when
Date: Fri, 10 Oct 2008 16:43:51 +0300 [thread overview]
Message-ID: <20081010134351.GL16289@zakalwe.fi> (raw)
In-Reply-To: <48EE6A2B.8030005@redhat.com>
On Thu, Oct 09, 2008 at 01:31:39PM -0700, Ulrich Drepper wrote:
> H. Peter Anvin wrote:
> > The dup2() behavior comes from the logical consequence of dup2()'s
> > "close on reuse"; one would think it would be logical for dup3() to
> > behave the same way.
>
> No. We deliberately decided on this change. Otherwise, what is the
> result of dup3(fd, fd, O_CLOEXEC)? There is no reason to use
> dup2(fd,fd), so why the hell somebody wants to defend this is beyond me.
The reason is: application programmers expect it to behave that way.
The interface is mostly targeted for typical application programmers,
and consistency decreases bugs. In this respect, it would be a good
idea for dup3() to have the same semantics. Doing that might not make
practical sense, but it is secondary to obviousness.
--
Heikki Orsila
heikki.orsila@iki.fi
http://www.iki.fi/shd
next prev parent reply other threads:[~2008-10-10 14:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 12:10 Michael Kerrisk
2008-10-09 17:21 ` H. Peter Anvin
2008-10-09 20:31 ` Ulrich Drepper
2008-10-09 20:43 ` H. Peter Anvin
2008-10-09 20:52 ` Ulrich Drepper
2008-10-09 20:57 ` H. Peter Anvin
2008-10-09 21:04 ` Ulrich Drepper
2008-10-10 5:04 ` Michael Kerrisk
2008-10-10 12:09 ` Bernd Petrovitsch
2008-10-10 12:15 ` Michael Kerrisk
2008-10-10 13:02 ` Bernd Petrovitsch
2008-10-10 13:15 ` Michael Kerrisk
2008-10-10 13:31 ` Bernd Petrovitsch
2008-10-10 5:01 ` Michael Kerrisk
2008-10-10 13:43 ` Heikki Orsila [this message]
[not found] <bl2EV-7G2-9@gated-at.bofh.it>
[not found] ` <bl7v3-5sk-17@gated-at.bofh.it>
[not found] ` <blasN-OS-9@gated-at.bofh.it>
[not found] ` <blaCu-Z0-11@gated-at.bofh.it>
[not found] ` <blaMj-18o-23@gated-at.bofh.it>
[not found] ` <blaMj-18o-21@gated-at.bofh.it>
[not found] ` <bliqg-2DH-1@gated-at.bofh.it>
2008-10-10 11:42 ` Bodo Eggert
2008-10-10 11:59 ` Michael Kerrisk
2008-10-10 13:19 ` Bodo Eggert
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=20081010134351.GL16289@zakalwe.fi \
--to=shdl@zakalwe.fi \
--cc=drepper@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®