From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin strptime() is missing "%s" which strftime() has
Date: Mon, 24 Jul 2017 17:02:00 -0000 [thread overview]
Message-ID: <824a586d-7a5f-a2d0-f88c-b8d33fbd9359@redhat.com> (raw)
In-Reply-To: <BY1PR09MB03436E115C205453E19F9D31A5BB0@BY1PR09MB0343.namprd09.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 978 bytes --]
On 07/24/2017 08:24 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>>>> But that's just scanning a decimal integer to time_t.
>>>
>>> It's not a question of whether I can or can't convert a string into an
>>> integer, rather it's a question about portability of code that uses %s
>
>> I see your point but... "portability" is kind of the wrong expression
>> here. If you have portability in mind, you should *not* use %s at all.
>
> The point is, if I can use "%s" with strftime() on Cygwin, then I should be able to use "%s" with strptime(),
> but currently there's a disconcert with that. Indeed, "%s" is a GNU extension yet it has been on Linux for years,
> so why not here but only 50%?
Demand. I patches strftime to add %s because Coreutils wanted it. But
coreutils doesn't use strptime, so I had no reason to add it.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-07-24 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 13:54 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 17:02 ` Eric Blake [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-24 21:48 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 22:12 ` Eric Blake
2017-07-24 22:51 ` Brian Inglis
2017-07-24 19:51 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 9:21 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 10:53 ` Corinna Vinschen
2017-07-24 21:02 ` Kaz Kylheku
2017-07-24 21:28 ` Hans-Bernhard Bröker
2017-07-24 23:18 ` Brian Inglis
2017-07-24 23:31 ` Kaz Kylheku
2017-07-25 18:27 ` Brian Inglis
2017-08-30 0:25 ` Brian Inglis
2017-07-23 11:38 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-23 21:18 ` Kaz Kylheku
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=824a586d-7a5f-a2d0-f88c-b8d33fbd9359@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
/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).