Re: Very unique need

You've still not really clarified your intent, but you appear to mean only large cities, in which case you can scrape much of this information from wikipedia as Time zone is a standard field in the RHS info box for cities. I'm sure you could piece together a simplified version of the rest as well.

Re: DateTimeX namespace?

I may be stating the obvious, but it also has the advantage of sounding like something that takes a licking and keeps on ticking. -- Free map of local environmental resources: http://CambridgeMA.GreenMap.org -- MOTD on Setting Orange, the 18th of The Aftermath, in the YOLD 3173: Environmentalism

Re: Simple math: partitioning the time between two DateTimes

Multiply? Can't you get the duration of the difference in seconds, divvy that up, and then repeatedly add it to the previous result? -- Free map of local environmental resources: http://CambridgeMA.GreenMap.org -- MOTD on Prickle-Prickle, the 73rd of Confusion, in the YOLD 3173: Any damn fool

Re: ANNOUNCE: DateTime.pm 0.31

- Switched some uses of die() to Carp::croak(), where Excellent, I've had to add in handlers for $SIG{__DIE__} locally. Given all its other dependencies, I'd wondered why DT shyed away from this most useful one ;-) - Removed all uses of UNIVERSAL::isa and UNIVERSAL::can. Is there a ticket number

DT::Format::Strptime %H

I've run into a bit a bit of a problem using a format containing %H with raw data. The data I have uses both 0:00 and 24:00, one being the beginning of the day, the other the end. I know that the docs state %H accepts 0-23, but it doesn't seem unreasonable that it ought to DWIM, and process 24:00

Misc. DT module interactions resulting in an infinite loop?

I've run into an odd issue with DateTime and Memoization (often necessary to get decent performance for processing 10-20k records with repeat dates). I've processed a lot of data this way but I recently ran into a few records that caused an infinite loop, below is some simplified sample code that

Re: DT::Format::Strptime %H

But it has everything to do with strptime, if DateTime has this (newer) POSIXMEHARDER style approach. There's no reason this roll-over couldn't be handled in the module. I see 24:00 as being an exceptional case, a rather common and concise means to specify a *whole* day, without having to do any

Scheduling FAQ?

What's the best way to iterate over Mondays, Tuesdays, and Thursdays between two dates?I checked the site and list archives but found nothing. My hunch is: my $days = DateTime::Event::Recurrence-weekly( days = [1,2,4], start=$DT1); my $iter =

Re: Scheduling FAQ?

Hmm, it's not even as simple as that... as I just (re)noticed the dox state This specifies a recurrence that happens at 10:30 on the day specified by start = $dt, and then every 11 days before and after $dt. When trying to figure out why that didn't work. Am I the only one who does

Re: Scheduling FAQ?

Ah yes, of course. Thanks! FWIW the goal is to determine the average percentage of time each several rooms is occupied for a given period/set of records on an hour by hour basis over a week. Doesn't that sound like fun? --

Re: Days between dates FAQ?

PS Of course, it'd be good if as_list was context sensitive so it could optimize that. -- H4sICNoBwDoAA3NpZwA9jbsNwDAIRHumuC4NklvXTOD0KSJEnwU8fHz4Q8M9i3sGzkS7BBrm OkCTwsycb4S3DloZuMIYeXpLFqw5LaMhXC2ymhreVXNWMw9YGuAYdfmAbwomoPSyFJuFn2x8 Opr8bBBidcc= -- MOTD on Sweetmorn, the 48th of

Re: DateTime performance

Unfortunately, it's a known problem that CentOS suffers from too (@[EMAIL PROTECTED]). This also makes reading error output incredibly difficult since a full screen is given to list @INC. Instead of a few folks who are upgrading systems having to set PERL5LIB everyone else has to recompile perl

Re: DateTime::Event::Crom command method

This was cross-posted on perlmonks and what seems like a reasonable respnse was given there: An option to specify whether or not to use a user field. -- H4sICNoBwDoAA3NpZwA9jbsNwDAIRHumuC4NklvXTOD0KSJEnwU8fHz4Q8M9i3sGzkS7BBrm