bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Assaf Gordon <assafgordon@gmail.com>
To: Alex Eulenberg <alex@rent-a-mind.com>, bug-gnulib@gnu.org
Subject: Re: [PATCH] ISO 8601 basic format and decimal hours, minutes
Date: Sun, 7 Apr 2019 01:20:41 -0600	[thread overview]
Message-ID: <8e527169-6d2b-805b-157f-893f78d324ab@gmail.com> (raw)
In-Reply-To: <20190219040013.14575-1-alex@rent-a-mind.com>

Hello Alex,

Thank for you putting the time for writing the patch
and descriptions in such details.

In general:

On 2019-02-18 9:00 p.m., Alex Eulenberg wrote:
> 1. Accept dates in the ISO 8601 basic date and time format.
[...]> 2. Accept decimal fractions of time units other than seconds in
> accordance with ISO 8601.
[...]
> Forms no longer accepted as a result of the patch:
[...]
> input                  current output              output with patch
> "20180102 00-03"       2018-01-02T03:00+00 +       (rejected)
> "20180102 04-03"       2018-01-02T07:00+00 +       (rejected)
[...]
> 
> input                  current output              output with patch
> "20180102T00-03"       (rejected)                  2018-01-02T03:00+00
> "20180102T04-03"       (rejected)                  2018-01-02T07:00+00

Adding new accepted formats is good,
but rejecting (or changing the meaning of) currently-accepted formats
is a much more problematic decision due to breaking existing programs.

I think that before continuing, it should be discussed and decided
whether this is acceptable or not (Paul, Jim?).

If we do go forward this this breaking-change, we should make sure
to announce it and communicate it properly to users of coreutils' date(1).

As a compromise, note that the 'parse_datetime2' function accepts
'flags' parameter (added in recent years). Perhaps a flag could
be specified if 'T' is always iso8601 or military time
(and then add an option to date(1) ).


> 2. For inputs of form "(YY)YYMMDD'T'hhmm" the current version of
> parse-datetime interprets the "T" as the single-letter military time zone
> identifier equivalent to zone offset +0700. This is probably never the
> intention.

Not so, 'T' has special handling code, and in some of the cases
is explicitly translated to HOUR(7):
https://git.savannah.gnu.org/cgit/gnulib.git/tree/lib/parse-datetime.y#n751


>   doc/parse-datetime.texi     |  17 ++--
>   lib/parse-datetime.y        | 193 ++++++++++++++++++++++++++++++------
>   tests/test-parse-datetime.c | 115 +++++++++++++++++++++
>   3 files changed, 291 insertions(+), 34 deletions(-)

As your contribution is significant (more than 10 lines),
a copyright assignment is required before we can review the patch (see 
https://www.gnu.org/licenses/why-assign.html ).

Please complete the following short form and send it to assign@gnu.org:

https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future

regards,
  - assaf








  parent reply	other threads:[~2019-04-07  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  4:00 [PATCH] ISO 8601 basic format and decimal hours, minutes Alex Eulenberg
2019-04-07  3:26 ` Alex Eulenberg
2019-04-07  7:20 ` Assaf Gordon [this message]
2019-04-08  5:05   ` Paul Eggert
2020-03-23  0:07   ` Alex Eulenberg

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8e527169-6d2b-805b-157f-893f78d324ab@gmail.com \
    --to=assafgordon@gmail.com \
    --cc=alex@rent-a-mind.com \
    --cc=bug-gnulib@gnu.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).