Great stuff!

It's a dozen plus years after this was written and it's still useful. There's a subtle bit introduced at the very end that should maybe be emphasized: these are DateTime objects we're dealing with, and the scalar variables are references to the underlying object, which can lead to some confusion if you let that fact slip your mind.

Consider the bit about math with dates at the end:

   my $dt1 = DateTime->now();
   my $dt2 = $dt1->clone->subtract( weeks => 1);

[download]

Miss the ->clone bit and you've got two references to the same DateTime object, one week subtracted from the original $dt1 value. Probably not what you had in mind.

Imagine expecting the following to DWIM: 

#!/usr/bin/perl -w
use strict;
use DateTime;

my ($start, $end, @dates);

$start = DateTime->new(day => 1, month => 1, year => 2017);
$end = DateTime->new(day => 31, month => 1, year => 2017);

while ($start <= $end) {
    # Skip weekends
    if ($start->day_of_week() > 5) {
    push(@dates, $start);
    }
    $start = $start->add(days => 1);
}

for (@dates) {
    print $_, $/;
}

[download]

See it? I've forgotten to clone my $start variable as I push it onto my stack. This code produces:

2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00
2017-02-01T00:00:00

[download]

All I needed to do was push(@dates, $start->clone()); and then I see what I meant:

2017-01-02T00:00:00
2017-01-03T00:00:00
2017-01-04T00:00:00
2017-01-05T00:00:00
2017-01-06T00:00:00
2017-01-09T00:00:00
2017-01-10T00:00:00
2017-01-11T00:00:00
2017-01-12T00:00:00
2017-01-13T00:00:00
2017-01-16T00:00:00
2017-01-17T00:00:00
2017-01-18T00:00:00
2017-01-19T00:00:00
2017-01-20T00:00:00
2017-01-23T00:00:00
2017-01-24T00:00:00
2017-01-25T00:00:00
2017-01-26T00:00:00
2017-01-27T00:00:00
2017-01-30T00:00:00
2017-01-31T00:00:00

[download]

I hope this helps someone else avoid a similar problem in the future -- even a dozen years from now :)

In reply to Re: Getting started with DateTime by snax
in thread Getting started with DateTime by monsterzero

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.