This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] manual: fopen with the x flag does not follow ISO C11
On 12/11/19 1:53 AM, Florian Weimer wrote:
I'm not sure about the “common practice” part. This would need
checking. I would just drop it.
Sure, that's fine. I installed the attached.
I left the "ISO C11" vs "ISO C" issue for some later time.
>From ef4e158c736d067304164c3daa763e4f425af248 Mon Sep 17 00:00:00 2001
From: Paul Eggert <eggert@cs.ucla.edu>
Date: Wed, 11 Dec 2019 09:34:06 -0800
Subject: [PATCH] manual: clarify fopen with the x flag
* manual/stdio.texi (Opening Streams): Say how glibc's
implementation of fopen with "x" follows ISO C11.
---
manual/stdio.texi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/manual/stdio.texi b/manual/stdio.texi
index bbd3061bab..8051603321 100644
--- a/manual/stdio.texi
+++ b/manual/stdio.texi
@@ -216,7 +216,9 @@ exists, @code{fopen} fails rather than opening it. If you use
file. This is equivalent to the @code{O_EXCL} option to the
@code{open} function (@pxref{Opening and Closing Files}).
-The @samp{x} modifier is part of @w{ISO C11}.
+The @samp{x} modifier is part of @w{ISO C11}, which says the file is
+created with exclusive access; in @theglibc{} this means the
+equivalent of @code{O_EXCL}.
@end table
The character @samp{b} in @var{opentype} has a standard meaning; it
--
2.23.0