Hi all,
let me make my query independent of now() for the time being.
use DateTime::Event::Cron;
$cron = DateTime::Event::Cron-from_cron(cron = ' 15 18 * * 1-5');
$new_cron = $cron-clone()-set_time_zone('Europe/Berlin');
$date = DateTime-new( year = 2004, month = 6, day = 30,
[EMAIL PROTECTED] wrote:
When I request the next scheduled event I expect always to obtain the same
instant time, possibly expressed in different time zone. Unfortunately I get
19:15 CEST and 18:15 CEST. Where am I getting it wrong?
When you ask for
(1) cron-set_time_zone( tz )-next( x )
Tim,
My understanding with the current behavior is that if you set the
time_zone for the set, that time zone will override the time zone of a
datetime argument. Probably the easiest thing for you to do is to *not*
set the time_zone of the set (since, as was previously discussed, it is
actually
Matt Sisk wrote:
My understanding with the current behavior is that if you set the
time_zone for the set, that time zone will override the time zone of a
datetime argument.
Besides, the time zone is being applied in the wrong order.
This should be fixed.
The current implementation only
On Wed, 30 Jun 2004, Flavio S. Glock wrote:
As for the factory vs. mutator, would anyone give a final word on
whether this should be changed?
The following DateTime::Set methods could be mutators:
set_time_zone
set( locale = ... )
add_duration
add( years = ... )
