: datetime@perl.org
Subject: Re: ISO 8601 Format -MM-DDThh:mm:ss.sss[+-]hhmm
Carl Vincent wrote:
Do you have any reference from the official standard to this consistency
issue in the format? If so, I can take it up with Salesforce, since they
claim they're standards compliant and that's what's
-Original Message-
From: Zefram [mailto:zef...@fysh.org]
Sent: 25 April 2012 11:04
To: Carl Vincent
Cc: datetime@perl.org
Subject: Re: ISO 8601 Format -MM-DDThh:mm:ss.sss[+-]hhmm
Carl Vincent wrote:
I can't see a case where the lack of a colon in the time offset
introduces ambiguity
Carl Vincent wrote:
$ DateTime::Format::ISO8601-parse_datetime('2012W144T10:39+');
2012-04-05T10:39:00
Oh, well spotted, that's entirely inconsistent. The input could correctly
be 2012-W14-4T10:39+00:00 or 2012W144T1039+.
-zefram
-Original Message-
From: Zefram [mailto:zef...@fysh.org]
Sent: 24 April 2012 18:14
To: datetime@perl.org
Cc: Carl Vincent
Subject: Re: ISO 8601 Format -MM-DDThh:mm:ss.sss[+-]hhmm
Thomas Klausner wrote:
Though I'm not sure why (beeing not familiar with the spec), my patch
was rejected
Carl Vincent wrote:
I can't see a case where the lack of a colon in the time offset
introduces ambiguity in the parsing. It may be poor style, but it's not
necessarily broken.
You've got to be careful about this sort of thing when there's an
actual standard. Once you start accepting something
Hi!
On Tue, Apr 24, 2012 at 03:50:27PM +, Carl Vincent wrote:
I'm looking to parse a datetime from ISO8601 use DateTime::Format::ISO8601
2012-04-24T10:39:00.000+
I had a similar problem once:
https://rt.cpan.org/Public/Bug/Display.html?id=52645
(I submitted a patch to RT, even
Thomas Klausner wrote:
Though I'm not sure why (beeing not familiar with the spec), my patch
was rejected.
ISO 8601 implies (but does not explicitly state) that you must be
consistent within a single expression about whether you use the
hyphen and colon separators (extended format). With the
