public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yann at droneaud dot fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/16088] Implement strptime %Z
Date: Mon, 08 Aug 2022 19:05:18 +0000 [thread overview]
Message-ID: <bug-16088-131-KUYrrU64OF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16088-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16088
Yann Droneaud <yann at droneaud dot fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yann at droneaud dot fr
--- Comment #2 from Yann Droneaud <yann at droneaud dot fr> ---
Created attachment 14265
--> https://sourceware.org/bugzilla/attachment.cgi?id=14265&action=edit
test case to demonstrate failure in parsing %Z format
(In reply to Ondrej Bilka from comment #0)
> A strptime %Z currently only reads timezone but ignores it. Actual
> implementation would be needed.
And unfortunately the way it ignores the timezone name makes strptime() unable
to parse names that are not delimited by white space.
For example strptime(, "%Z/",) will return NULL, because the trailing slash
will be consumed as the timezone name.
This corner case makes strptime() unable to parse strftime() output:
strftime() produced "GMT/"
strptime() failed to parse "GMT/"
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-08 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 17:12 [Bug libc/16088] New: " neleai at seznam dot cz
2014-03-11 7:20 ` [Bug libc/16088] " allachan at au1 dot ibm.com
2014-06-13 12:30 ` fweimer at redhat dot com
2015-01-27 14:02 ` vincent at bernat dot im
2015-08-27 22:18 ` [Bug time/16088] " jsm28 at gcc dot gnu.org
2022-08-08 19:05 ` yann at droneaud dot fr [this message]
2023-06-22 13:48 ` lancasterharp at gmail dot com
2023-06-22 15:15 ` lancasterharp at gmail dot com
2023-06-23 8:54 ` sam at gentoo dot org
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=bug-16088-131-KUYrrU64OF@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).