public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xiyou dot wangcong at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11312] popen should ignore 'b' in mode
Date: Tue, 23 Feb 2010 09:45:00 -0000	[thread overview]
Message-ID: <20100223094540.966.qmail@sourceware.org> (raw)
In-Reply-To: <20100222232719.11312.ebb9@byu.net>


------- Additional Comments From xiyou dot wangcong at gmail dot com  2010-02-23 09:45 -------
(In reply to comment #0)
> For consistency with fopen and freopen, it would be nice if popen(cmd,"rb")
> behaved like popen(cmd,"r") rather than failing with EINVAL.  In particular, the
> extension of supporting 'b' in the mode argument is already provided by Cygwin
> (although in cygwin, it actually makes a difference between text and binary
> pipes).  POSIX does not forbid this extension.
> 
> The request to allow applications to blindly request binary mode, even though it
> is otherwise a no-op in glibc, was first made here:
> http://lists.gnu.org/archive/html/bug-gnulib/2010-02/msg00195.html
> 
> Likewise, it would be nice if other fopen extension flags were gracefully
> handled (silently ignore 'm', 'x', and honor 'c'), since 'e' is already a common
> extension between both fopen and popen.  There is already precedence for this,
> since fdopen silently ignores 'x'.

It seems that ignoring 'b' makes sense.

Patch below does this.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11312

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2010-02-23  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 23:27 [Bug libc/11312] New: " ebb9 at byu dot net
2010-02-23  9:45 ` xiyou dot wangcong at gmail dot com [this message]
2010-02-23  9:46 ` [Bug libc/11312] " xiyou dot wangcong at gmail dot com
2010-02-24  0:16 ` bkorb at gnu dot org
2010-04-05 18:39 ` drepper at redhat dot com
2010-04-05 21:06 ` bkorb at gnu dot org
     [not found] <bug-11312-131@http.sourceware.org/bugzilla/>
2014-06-30 18:45 ` fweimer at redhat dot com
2014-06-30 19:20 ` eblake at redhat dot com

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=20100223094540.966.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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).