Dave Rolsky [EMAIL PROTECTED] wrote:
On Fri, 20 Jun 2003, Eugene van der Pijll wrote:
Peter J. Acklam schreef:
I could have sworn the difference was 0 seconds between 1970-01-01
and until the leap second in June 1972. I should have checked
ftp://maia.usno.navy.mil/ser7/tai
Eugene van der Pijll [EMAIL PROTECTED] wrote:
Peter J. Acklam schreef:
It is the IERS (http://www.iers.org) who decides when leap
seconds are inserted. According to their page
http://www.iers.org/iers/earth/rotation/utc/table1.html
the first leap second after 1970
John Peacock [EMAIL PROTECTED] wrote:
Peter J. Acklam wrote:
I don't see what the epoch has got to do with it. The TAI
time system is exactly like UTC except for the leap seconds,
and that, to me, seems very similar to what Perl is using.
The epoch has everything to do with it. TAI
use 1) since expanded formats should not be
used unless there is an agreement to use them.
Peter
--
Peter J. Acklam - [EMAIL PROTECTED] - http://home.online.no/~pjacklam
John Peacock [EMAIL PROTECTED] wrote:
Peter J. Acklam wrote:
Perl's gmtime() and localtime() aren't UTC compatible.
I'd say they are using TAI time. GMT belongs to the past.
Except you'd be wrong. ;~)
Conveniently for me, the pages you quote back me up, not you.
GMT == UTC for all
John Peacock [EMAIL PROTECTED] wrote:
Peter J. Acklam wrote:
I didn't mean that Perl is using a TAI library, but the TAI
time system or TAI calendar.
Perl is _not_ using TAI, since it is employing an epoch
corresponding to the Unix epoch (except on Mac's???).
I don't see what the epoch
Eugene van der Pijll [EMAIL PROTECTED] wrote:
If Perl (or the underlying library functions) used TAI, it
should have printed something like
$ perl -wle 'print scalar localtime $_ for 78796799 .. 78796801'
Sat Jul 1 01:00:09 1972
Sat Jul 1 01:00:10 1972
Sat Jul 1 01:00:11
John Peacock [EMAIL PROTECTED] wrote:
When I made a very simple attempt at this back in January, I limited myself to
the most basic format:
if ( @date =
( $val =~ /(\d\d\d\d) # year with century
-? # possible hyphen
(\d\d)
Dave Rolsky [EMAIL PROTECTED] wrote:
My article about date/time handling with Perl is now on perl.com at
http://www.perl.com/pub/a/2003/03/13/datetime.html
You write:
UTC is a good standard for the _internal_ representation of
dates and times, as it makes comparing datetimes or doing
Rick Measham [EMAIL PROTECTED] wrote:
Dave Rolsky at [EMAIL PROTECTED] spake thus:
Is that acceptable? I can't think of any good solutions to
this, other than documenting it.
Bloody stupid idea this daylight-savings crap.
You run into essentially the same problems when dealing with leap
Eugene van der Pijll [EMAIL PROTECTED] wrote:
I've just uploaded version 0.02 of DateTime::Calendar::Julian,
incorporating the comments of Tatsuhiko Miyagawa, Dave Rolsky
and others. All feedback is of course welcome.
Eugene
From the change log:
0.02 2003-02-16
- replaced
--
Peter J. Acklam - [EMAIL PROTECTED] - http://home.online.no/~pjacklam
;
}
Peter
--
Peter J. Acklam - [EMAIL PROTECTED] - http://home.online.no/~pjacklam
[EMAIL PROTECTED] (Dave Rolsky) wrote:
Joshua Hoblitt wrote:
Are you planning on requiring XS for DT or also maintaining a
pure Perl implementation?
Good question. I could maintain the pure Perl code as well, but
it's kind of a pain. I think that if the DateTime project is to
succeed,
)) || ! ($_[0] % 400);
}
Peter
--
Peter J. Acklam - [EMAIL PROTECTED] - http://home.online.no/~pjacklam
[EMAIL PROTECTED] (Dave Rolsky) wrote:
My only point was that according to Calendrical Calculations, the
Gregorian calendar, when extended backwards before 1582 [...]
This is known as the proleptic (sometimes spelt prolaptic)
Gregorian calendar. Ditto with the Julian calendar.
Peter
--
Eugene van der Pijll [EMAIL PROTECTED] wrote:
ISO8601 obviously uses the astronomical convention. Dave
evidently uses the Dionysian reckoning. I think this is the
correct choice: if I want to create a date in 44BC, I'd prefer
to say
$dt = DateTime-new( year = -44, month = 3, day =
Dave Rolsky [EMAIL PROTECTED] wrote:
On Wed, 12 Feb 2003, Eugene van der Pijll wrote:
Interestingly, the function ymd (and therefore also iso8601)
uses astronomical years. Obviously correct for iso8601; I'm
not sure about ymd.
That's a bug.
So is the output of the iso8601 method when
[EMAIL PROTECTED] (Dave Rolsky) wrote:
On Wed, 12 Feb 2003, Peter J. Acklam wrote:
Alas, the current API is a bastard -- an odd mixture of the two
and doesn't match *any* convention: It doesn't match the 44 BC-
type notation since you have to use a leading - rather than the
trailing BC
[EMAIL PROTECTED] (Eugene Van Der Pijll) wrote:
Peter J. Acklam schreef:
The code
my $dt = DateTime-new( year = -7 );
print $dt-iso8601(), \n;
prints
-006-01-01T00:00:00
but ISO 8601 requires at least four digits in the year.
No. I haven't read ISO 8601
[EMAIL PROTECTED] (Rick Measham) wrote:
Maybe new() takes an optional ISOyear parameter? Thus the
default 'year' is the way we commonly think of it and can take
optional BC/BCE/AD/CE coding. It treats -1 as 1 BC and dies on
getting '0'. ISOyear can only take integers with an optional
'-'.
I
[EMAIL PROTECTED] (Rick Measham) wrote:
There are two time periods that do not change: Years (time the
earth takes to travel around the sun) and Days (time the earth
take to spin one complete revolution). I'd suggest that these
the the two values that DateTime keeps internally. The 'year'
Rich Bowen [EMAIL PROTECTED] wrote:
On Tue, 28 Jan 2003, Peter J. Acklam wrote:
[I know this is a very old posting, but I just can't resist
commenting it since it is about the base time format.]
It seems a little irrelevant, and perhaps even unfair, to start
rebutting comments that I
[EMAIL PROTECTED] (Rich Bowen) wrote:
On Sun, 6 May 2001 03:35:15 +0530, Abhijit Menon-Sen said:
Have you seen the TAI64* formats at URL:http://cr.yp.to/time.html?
(I am supposedly writing Time::TAI64.)
Hmm. attosecond accuracy? What real-world application really
needs that sort of
[EMAIL PROTECTED] (Eugene Van Der Pijll) wrote:
Timestamps with a precision better than an attosecond are never
needed, as far as I know. Physicists work with as, ys and zs,
but only with time lengths or intervals, not with absolute time.
That's probably true -- and the example I gave was,
Where can I download older postings from [EMAIL PROTECTED]?
I have been searching but not found anything. It would be nice
if older postings were archived somewhere for downloading.
I am new here and I would like to be up to date to avoid
posting questions and comments which have already been
26 matches
Mail list logo
