From: Martin Sebor <msebor@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: PING [PATCH] mention disabling GCC built-ins for customization
Date: Fri, 29 Jun 2018 17:01:00 -0000 [thread overview]
Message-ID: <2748d985-0104-92c9-102b-344ff916f0c1@gmail.com> (raw)
In-Reply-To: <cd8d1682-9a94-2c33-f9a9-7b6d94c72b53@gmail.com>
I have committed the change:
http://tinyurl.com/y7jbvfs4
Martin
On 06/27/2018 05:37 PM, Martin Sebor wrote:
> Ping: https://sourceware.org/ml/libc-alpha/2018-06/msg00428.html
>
> If there are no further comments I'd like to commit this change
> later this week.
>
> On 06/14/2018 01:11 PM, Martin Sebor wrote:
>> On 06/14/2018 01:25 AM, Andreas Schwab wrote:
>>> On Jun 13 2018, Martin Sebor <msebor@gmail.com> wrote:
>>>
>>>> diff --git a/manual/stdio.texi b/manual/stdio.texi
>>>> index 38be236..d945955 100644
>>>> --- a/manual/stdio.texi
>>>> +++ b/manual/stdio.texi
>>>> @@ -2963,7 +2963,11 @@ The facilities of this section are declared in
>>>> the header file
>>>>
>>>> @strong{Portability Note:} The ability to extend the syntax of
>>>> @code{printf} template strings is a GNU extension. ISO standard C has
>>>> -nothing similar.
>>>> +nothing similar. When using the GNU C compiler or any other compiler
>>>> +that interprets calls to standard I/O functions according to the rules
>>>> +of the language standard it is necessary to disable such handling by
>>>> +the appropriate compiler option. Otherwise the behavior of a program
>>>> +that relies on the extension is undefined.
>>>
>>> The manual already says that redefining existing conversions causes
>>> problems:
>>>
>>> You can redefine the standard output conversions, but this is
>>> probably
>>> not a good idea because of the potential for confusion. Library
>>> routines
>>> written by other people could break if you do this.
>>>
>>> We should extend that with a stronger language, independent of any
>>> compiler behaviour.
>>
>> That sounds fine to me. Attached is an updated patch that also
>> adds text to this paragraph. I added a Portability Note before
>> the text to highlight the portability impact, similarly to
>> the prior paragraph.
>>
>> Martin
>
prev parent reply other threads:[~2018-06-29 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 18:19 Martin Sebor
2018-06-13 20:35 ` Florian Weimer
2018-06-13 20:55 ` Martin Sebor
2018-06-13 21:01 ` Florian Weimer
2018-06-13 21:31 ` Martin Sebor
2018-06-14 7:25 ` Andreas Schwab
2018-06-14 19:11 ` Martin Sebor
2018-06-18 7:42 ` Andreas Schwab
2018-06-19 3:00 ` Martin Sebor
2018-06-27 23:37 ` PING " Martin Sebor
2018-06-29 17:01 ` Martin Sebor [this message]
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=2748d985-0104-92c9-102b-344ff916f0c1@gmail.com \
--to=msebor@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).