Why does the DateTime::Set class need to get both
dates back? I think that's what is confusing me.
Another option: the callback receives a start date
and an end date parameters, and it returns the list
of the dates that are in that time span. This looks
much simpler, and it solves the
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
Peter J. Acklam wrote:
You run into essentially the same problems when dealing with leap
seconds -- which any software using UTC should be able to handle.
For instance, what is one day after 1998-12-31 25:59:60 UTC? Is
it 1999-01-01 25:59:59 UTC or 1999-01-02 00:00:00 UTC?
I think you mean
On Monday, March 10, 2003, at 04:26 PM, Dave Rolsky wrote:
my $dt = DateTime-new( year = 2003, month = 4, day = 5,
hour = 2, time_zone = 'America/Chicago',
$dt-add( days = 1 );
then the code will throw an exception, because there is no local 2:00
AM
on 2003-04-06 in
Heyo,
Any chance of set_time_zone() being able to return $self?
I just ask since it would make possible code such as:
my $dt = DateTime-from_epoch( epoch = $then )-set_time_zone( $tz );
Rather than having to split it into two, less associated, lines.
An appropriate patch is attached. Well,
On Wed, 12 Mar 2003, Iain 'Spoon' Truskett wrote:
Any chance of set_time_zone() being able to return $self?
I just ask since it would make possible code such as:
my $dt = DateTime-from_epoch( epoch = $then )-set_time_zone( $tz );
Rather than having to split it into two, less associated,
