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.
  • by echo (2881) on 2003.11.07 4:38 (#25567)
    If you're using a 0.x module you need to be extra careful about what's going on while the authors adjust their API. If authors can't twiddle the API while in 0.x, when can they? I've been using DateTime in production since version 0.03. More than once I've had to change my code because DateTime's API was tweaked, but to me it's well worth it because it's a great module, and because the authors are very reponsive and the changes well documented. Following the datetime dev list helps too, and that's where I learned that int($d1->jd) - int($d2->jd) was what I wanted for days difference. If you can't be bothered to put in that extra time that using a 0.x module requires then you should stick to other, stable CPAN date modules, and/or wait for DateTime 1.0.
    • If you're using a 0.x module you need to be extra careful about what's going on while the authors adjust their API.

      A fair point.

      Seeing as I was testing against the current version that installed on Windows and the same version on my Linux box, I wasn't aware of the change. I will try to be a bit more careful in future.