Was there a compelling reason not to have a class method analagous to
DefaultLocale() for timezones, such as DefaultTimezone()?
And if it were present, am I alone in finding it useful for the Format
modules, such as DT::F::MySQL, where the zoneless strings are forced
into the 'floating' timezon
On Wed, 5 Nov 2003, Matt Sisk wrote:
> Was there a compelling reason not to have a class method analagous to
> DefaultLocale() for timezones, such as DefaultTimezone()?
Nope, no particular reason. But thinking about it, it seems like a bad
idea. Locale is something that I would think the end us
On Wed, 5 Nov 2003, Matt Sisk wrote:
> And as a convenience, I was suggesting this as equivalent:
>
> $dt3 = $dt1->clone(%overrides);
If the set() method accepted a time_zone parameter (which is trivial to
add), wouldn't this be equivalent to:
$dt3 = $dt1->clone->set(%overrides);
??
-dave
/
At 21:57 -0600 2003-11-05, Matt Sisk wrote:
Rick Measham wrote:
The problem above is that $dt->parameters() may return a key
included in %overrides. So how about $dt->parameters( %overrides )?
As I corrected myself earlier, I should have made the $dt in
$dt->parameters() more generic, rather t
On Thu, 6 Nov 2003, Rick Measham wrote:
> But the same problem exists ... %parms will contain locale =>
> 'en_AU', so your call to set is now:
>
> $dt3->set( locale=>'en_AU', year=>2003 .. second => 27, time_zone => '-1100',
> locale=>'latvia'
> );
>
> So which locale gets used?
The s
