public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com, "Lavrentiev,
	Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
Subject: Re: Cygwin strptime() is missing "%s" which strftime() has
Date: Mon, 24 Jul 2017 22:12:00 -0000	[thread overview]
Message-ID: <f73a8d58-edc5-b9ee-86c8-e44dbd3d3944@redhat.com> (raw)
In-Reply-To: <BY1PR09MB0343072DC1C2667AAD1EEFF0A5BB0@BY1PR09MB0343.namprd09.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 1465 bytes --]

On 07/24/2017 04:28 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> then its use of %s in either of those functions constitutes a _bug_
> 
> Oh really?  Is that why "%s" was added to Cygwin's strftime() lately?

Your mailer is breaking up threads, which is making it very annoying to
follow where your replies are landing.

strftime() has been formatting %s since Oct 2015 (if you can call that
"lately").  In fact, you made me check git history: it was not me that
added it (like I thought, so I must have added it in gnulib instead);
but Brian - in fact, the same Brian who is now working on adding %s to
strptime().

The point remains: if you want your program to be portable, you should
not use %s.  But if your program is okay with demanding a GNU/Linux
environment rather than sticking to portable code, then Cygwin still
tries to cater to that by providing as many GNU/Linux extensions as
possible, and pointing out where we fall short is appreciated.  But
still, someone has to code it, this is a volunteer effort, and we tend
to scratch our own itches.  The fact that strptime() lagged strftime()
by nearly 2 years in adding %s support is par for the course.  It's not
worth complaining about, and if you want faster action, then submit
patches yourself instead of asking others to do it for you.

-- 
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 --]

  reply	other threads:[~2017-07-24 21:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 21:48 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 22:12 ` Eric Blake [this message]
2017-07-24 22:51   ` Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2017-07-24 19:51 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 13:54 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 17:02 ` Eric Blake
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=f73a8d58-edc5-b9ee-86c8-e44dbd3d3944@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    --cc=lavr@ncbi.nlm.nih.gov \
    /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).