On Mon, 13 Jan 2003, Yitzchak Scott-Thoennes wrote:
> >Let's say that if you create a DateTime object with specifying a timezone,
> >it just uses UTC. Wouldn't that achieve the same effect? In other words,
> >if you created a datetime of "2002-12-15 19:00:00" and never changed the
> >timezone associated with it, then it would always represent 6PM on that
> >date.
>
> That's exactly the same blurring of distinction that Date::ICal
> suffers from. In iCalendar talk, "20030113T190000Z" is a UTC time and
> "20030113T190000" (without a TZID set) is a floating time, and they
> should be representable with different objects. I would expect that
> if you add a timezone to them, say America/New_York, you would get
> "TZID=America/New_York:20030113T140000" for the first and
> "TZID=America/New_York:20030113T190000" for the second.
Aha! I get it. In that case, I think we need a special "floating"
timezone, so you can say something like this:
my $dt = DateTime->new( year => 2003, month => 1, day => 13, hour => 19,
timezone => 'floating' );
# or DateTime::TimeZone->new( zone => 'floating' )
-dave
/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/
