From: Mike Frysinger <vapier@gentoo.org>
To: Vincent Bernat <Vincent.Bernat@exoscale.ch>
Cc: libc-alpha@sourceware.org, Vincent Bernat <vincent@bernat.im>
Subject: Re: [PATCH] time: in strptime(), make %z accept [+-]HH:MM time zones
Date: Fri, 06 Mar 2015 10:21:00 -0000 [thread overview]
Message-ID: <20150306102144.GV12857@vapier> (raw)
In-Reply-To: <1422372004-32522-1-git-send-email-Vincent.Bernat@exoscale.ch>
[-- Attachment #1: Type: text/plain, Size: 2373 bytes --]
On 27 Jan 2015 16:20, Vincent Bernat wrote:
> In ISO 8601, +03:30 is a valid time zone. Currently, strptime() only
> parses it as a 2-digit time zone an believes this is +03:00. This change
> makes it accept a single semi-colon.
err, nowhere that i see here do you parse a semi-colon. i guess you meant
"colon" ?
i think you're colliding with the fix for BZ #16141. i'd prefer to merge
that first though, so you might want to rebase once that's done.
> This fix BZ #17887.
you should include [BZ #17887] in the subject line too
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -3,6 +3,9 @@
> [BZ #17886]
> * time/strptime_l.c: Make %z accept Z as a valid time zone.
>
> + [BZ #17887]
> + * time/strptime_l.c: Make %z accept [+-]HH:MM time zones.
each patch should get a standalone entry. that means you'd add another
date/name line above this.
also you should scope your changes a bit. that means this would be:
* time/strptime_l.c (__strptime_internal): .....
> + /* We recognize four formats: 1. if two digits are given,
> + these specify hours. 2. If fours digits are used,
> + minutes are also specified. 3. A semi-colon can be used
> + to separate the two groups of two digits (HH:MM). 4. 'Z'
> + is equivalent to +0000. */
needs two spaces after the periods
> @@ -765,8 +767,16 @@ __strptime_internal (rp, fmt, tmp, statep LOCALE_PARAM)
> return NULL;
> bool neg = *rp++ == '-';
> int n = 0;
> - while (n < 4 && *rp >= '0' && *rp <= '9')
> + while (n < 4 &&
> + ((*rp >= '0' && *rp <= '9') ||
> + (*rp == ':' && n == 2)))
> {
> + if (*rp == ':')
> + {
> + rp++;
> + if (!(*rp >= '0' && *rp <= '9'))
> + return NULL;
> + }
> val = val * 10 + *rp++ - '0';
> ++n;
> }
indentation is broken -- needs to start with a tab
not exactly a new issue, but probably should be using isdigit() here
i think the loop might be cleaner if you didn't duplicate the checks.
i.e. something like this (ignoring style, and this is untested):
while (n < 4) {
if (n == 2 && *rp == ':')
++rp;
if (!isdigit (*rp))
return NULL;
val = val * 10 + *rp++ - '0';
++n;
}
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-06 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 15:20 [PATCH] time: ensure failing strptime() tests are reported correctly Vincent Bernat
2015-01-27 16:02 ` [PATCH] time: in strptime(), make %z accept Z as a time zone Vincent Bernat
2015-03-06 10:11 ` Mike Frysinger
2015-01-27 16:03 ` [PATCH] time: in strptime(), make %z accept [+-]HH:MM time zones Vincent Bernat
2015-03-06 10:21 ` Mike Frysinger [this message]
2015-03-06 11:06 ` Vincent Bernat
2015-04-20 11:42 ` [BZ #17887][PATCH] " Vincent Bernat
2015-03-06 10:04 ` [PATCH] time: ensure failing strptime() tests are reported correctly Mike Frysinger
2015-03-06 11:02 ` Vincent Bernat
2015-03-06 11:07 ` Mike Frysinger
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=20150306102144.GV12857@vapier \
--to=vapier@gentoo.org \
--cc=Vincent.Bernat@exoscale.ch \
--cc=libc-alpha@sourceware.org \
--cc=vincent@bernat.im \
/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).