Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'm thinking of re-building Time::Piece on top of Date::ICal, which has very cool support for adding and subtracting times and doing periodic events.

    Is there anything that a combination of those two would miss?
    • Here's a quick summary of what I think the "uber-date/time" module would look like:

      - Date objects

      -- Simple OO interface for doing basic things. I like how Time::Piece does this.

      -- Date math via overloading. Time::Piece and Time::Seconds are not bad. Looks like Date::ICal has support for more complex date math.

      -- Works outside of epoch times. Date::ICal does this.

      -- Simple date parsing. Time::Piece->strptime plus the functionality of Date::Parse would be good.

      -- Complex date parsing. Date::Man
      • I think that this is a great idea, overall. My only requests would be that a) the different functionalities be in related modules, so that you only load what you need; and b) that it be fast -- very fast.

        Perhaps you should start a project or at least a discussion list of some kind so that interested parties can contribute and collaborate on a design spec? I'd sign up. Hopefully Matts would have time to participate, too!

        --David