| … | |
… | |
| 1058 | # Time::Piece::Strptime uses the "incredibly flexible date parsing routine" |
1058 | # Time::Piece::Strptime uses the "incredibly flexible date parsing routine" |
| 1059 | # from FreeBSD, which can't parse ISO 8601, RFC3339, RFC4287 or much of anything |
1059 | # from FreeBSD, which can't parse ISO 8601, RFC3339, RFC4287 or much of anything |
| 1060 | # else either. Whats incredibe over standard strptime totally escapes me. |
1060 | # else either. Whats incredibe over standard strptime totally escapes me. |
| 1061 | # doesn't do fractional times, either. sigh. |
1061 | # doesn't do fractional times, either. sigh. |
| 1062 | # In fact, it's all a lie, it uses whatever strptime it wants, and of course, |
1062 | # In fact, it's all a lie, it uses whatever strptime it wants, and of course, |
| 1063 | # they are all incomptible. The openbsd one simply ignores %z (but according to the |
1063 | # they are all incompatible. The openbsd one simply ignores %z (but according to the |
| 1064 | # docs, it would be much more incredibly flexible indeed. If it worked, that is.). |
1064 | # docs, it would be much more incredibly flexible indeed. If it worked, that is.). |
| 1065 | scalar eval { |
1065 | scalar eval { |
| 1066 | my $s = $_[1]; |
1066 | my $s = $_[1]; |
| 1067 | |
1067 | |
| 1068 | $s =~ s/Z$/+00:00/; |
1068 | $s =~ s/Z$/+00:00/; |
