From: "Dmitry V. Levin" <ldv@altlinux.org>
To: libc-alpha@sourceware.org
Subject: Re: [RFC][PATCH v2 3/6] Implement the %OB specifier - alternative month names (bug 10871)
Date: Wed, 01 Jun 2016 10:42:00 -0000 [thread overview]
Message-ID: <20160601104220.GA1077@altlinux.org> (raw)
In-Reply-To: <666336576.426212.9ea90152-1d54-4eec-8ffa-81bfd328d92b.open-xchange@poczta.nazwa.pl>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Wed, Mar 30, 2016 at 01:31:21AM +0200, Rafal Luzynski wrote:
> 29.03.2016 16:31 "Dmitry V. Levin" <ldv@altlinux.org> wrote:
> > On Fri, Mar 25, 2016 at 01:55:13AM +0100, Rafal Luzynski wrote:
> > [...]
> > > This means that all applications using %B to retrieve the month
> > > name standalone should use %OB from now.
> >
> > Such applications as cal(1) would not be able to print month names
> > properly in a way that would work with different glibc versions.
> > Looks like this is a change incompatible in both ways.
>
> Yes, that's exactly what will happen. Such applications must be
> updated. They must start using strftime("%OB") and nl_langinfo(ALTMON_...).
> They must either detect the glibc version at runtime and choose
> the correct format specifier or require the minimum glibc version
> at build time. I'm willing to contact the upstream developers and
> provide the instructions how to change their applications.
In glibc, we don't make changes this way. If an incompatible ABI change
is introduced, the old ABI remains for compatibility with software linked
with it.
With regards to runtime checks, could you give an example of such a check?
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-01 10:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 0:55 Rafal Luzynski
2016-03-29 9:02 ` Florian Weimer
2016-03-29 10:59 ` keld
2016-11-04 13:36 ` Florian Weimer
2016-11-05 10:42 ` Rafal Luzynski
2016-03-29 14:15 ` Carlos O'Donell
2016-03-29 23:23 ` Rafal Luzynski
2016-03-29 14:31 ` Dmitry V. Levin
2016-03-29 23:31 ` Rafal Luzynski
2016-06-01 10:42 ` Dmitry V. Levin [this message]
2016-06-01 21:51 ` Rafal Luzynski
2016-06-01 22:20 ` Paul Eggert
2016-06-01 23:54 ` Rafal Luzynski
2016-06-02 7:03 ` Paul Eggert
2016-06-03 7:08 ` Rafal Luzynski
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=20160601104220.GA1077@altlinux.org \
--to=ldv@altlinux.org \
--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).