From: Florian Weimer <fweimer@redhat.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH v4 06/11] Provide backward compatibility for strftime family (bug 10871).
Date: Mon, 07 Nov 2016 14:13:00 -0000 [thread overview]
Message-ID: <238ab162-7ff7-d90e-9f95-630ac413a064@redhat.com> (raw)
In-Reply-To: <1458120697.2205845.1478343189427@poczta.nazwa.pl>
On 11/05/2016 11:53 AM, Rafal Luzynski wrote:
> 4.11.2016 14:40 Florian Weimer <fweimer@redhat.com> wrote:
>>
>>
>> On 10/28/2016 02:49 AM, Rafal Luzynski wrote:
>>> As %OB format specifier has been added to strftime/wcsftime
>>> family of functions backward compatibility implementation must be
>>> provided for older binaries which assume that %B returns
>>> a month name in the nominative case.
>>
>> I think this is a misuse of symbol versioning. Why would I want to pick
>> up this change when compiling from source, but not for existing binaries?
>>
>> Florian
>
> There may be applications which rely on the fact that "%B"
> returns the month name in a nominative case. An example is cal(1)
> which has been pointed out in [1]. Their source code should be
> changed to use "%OB" but it cannot be expected from the existing
> binaries.
> You could also ask how to provide the backward compatibility
> for the applications compiled from source.
Yes, that's what I'm concerned about.
> I think it's impossible and it's been kinda agreed in [2].
I think we should strive to provide backwards compatibility for
applications and not alter the meaning of %B, and rather change %c to
use %OB (or whatever the source of the month name in genitive ends up to
be) instead of %B.
One example where this matters is German. If POSIX requires that %B
returns the genitive case, as has been suggested, then all applications
which currently use %B are broken because I have yet to see a
mechanically generated German date string which actually needs the
genitive case. In current usage, they only occur in phrases such âon
the last Sunday of Novemberâ.
Does this clarify my position?
Thanks,
Florian
next prev parent reply other threads:[~2016-11-07 14:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 0:49 Rafal Luzynski
2016-11-04 13:40 ` Florian Weimer
2016-11-05 10:53 ` Rafal Luzynski
2016-11-07 14:13 ` Florian Weimer [this message]
2016-11-08 11:39 ` Rafal Luzynski
2016-11-09 10:49 ` Florian Weimer
2016-11-10 0:33 ` Rafal Luzynski
2016-11-10 12:41 ` Florian Weimer
2016-11-10 18:42 ` Rafal Luzynski
2016-11-10 19:19 ` Andreas Schwab
2016-11-15 1:21 ` Rafal Luzynski
2016-11-11 3:52 ` Rical Jasan
2016-11-15 1:38 ` Rafal Luzynski
2016-11-15 11:09 ` Rafal Luzynski
2016-11-16 13:06 ` Rical Jasan
2016-11-17 11:18 ` Rafal Luzynski
2016-11-18 9:22 ` Rical Jasan
2016-11-22 23:56 ` Rafal Luzynski
2016-11-09 11:00 ` Florian Weimer
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=238ab162-7ff7-d90e-9f95-630ac413a064@redhat.com \
--to=fweimer@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@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).