From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin strptime() is missing "%s" which strftime() has
Date: Mon, 24 Jul 2017 10:53:00 -0000 [thread overview]
Message-ID: <20170724092136.GA27514@calimero.vinschen.de> (raw)
In-Reply-To: <BY1PR09MB0343663DE41D927E67CF0CCEA5BB0@BY1PR09MB0343.namprd09.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
On Jul 24 02:09, 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.
%s is a GNU extension and as such, is not portable by definition.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-07-24 9:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 9:21 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 10:53 ` Corinna Vinschen [this message]
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
-- 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 13:54 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2017-07-24 17:02 ` Eric Blake
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=20170724092136.GA27514@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).