public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "allachan at au1 dot ibm.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/12836] fmemopen(buf,size,"w+b") isn't binary
Date: Thu, 30 Jan 2014 03:50:00 -0000	[thread overview]
Message-ID: <bug-12836-131-SgmIGzPsPM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12836-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=12836

paxdiablo <allachan at au1 dot ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |allachan at au1 dot ibm.com

--- Comment #5 from paxdiablo <allachan at au1 dot ibm.com> ---
The POSIX standard calls for fmemopen() to accept all mode strings as allowed
in fopen() but notes that use of "b" results in implementation-defined
behaviour.

So, technically, I think an implementation _could_ treat w+b and wb+ as
different if it so desired but it would have to document that.

Of course, it would probably be easier to fix the code to make them identical
:-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-01-30  3:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 15:12 [Bug libc/12836] New: " eblake at redhat dot com
2011-06-02 15:13 ` [Bug libc/12836] " eblake at redhat dot com
2011-07-23  4:00 ` drepper.fsp at gmail dot com
2011-07-27 17:59 ` eblake at redhat dot com
2012-02-21  2:15 ` [Bug stdio/12836] " jsm28 at gcc dot gnu.org
2012-04-28  2:24 ` mtk.manpages at gmail dot com
2014-01-30  3:50 ` allachan at au1 dot ibm.com [this message]
2014-01-30  4:23 ` eblake at redhat dot com
2014-01-30  4:25 ` eblake at redhat dot com
2014-06-27 13:13 ` fweimer at redhat dot com
2015-07-08 15:15 ` adhemerval.zanella at linaro dot org

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=bug-12836-131-SgmIGzPsPM@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).