I very rarely use Date::Parse or Date::Manip. The core module Time::Piece usually does everything I need. Here is an SSCCE showing it correctly parsing the two sample dates which you gave in your prose (but which do not appear in your code sample).

use strict;
use warnings;

use Time::Piece;
use Test::More tests => 6;

my $str = '31/08/2024';

my $tp = Time::Piece->strptime ($str, '%d/%m/%Y/');
is $tp->mday, 31;
is $tp->mon, 8;
is $tp->year, 2024;

$str = '01/09/2024';

$tp = Time::Piece->strptime ($str, '%d/%m/%Y/');
is $tp->mday, 1;
is $tp->mon, 9;
is $tp->year, 2024;

[download]

If you want to persist with Date::Parse and/or Date::Manip that's fine but you will doubtless help others to help you by showing the problem as an SSCCE like this.

🦛

In reply to Re: date parsing by hippo
in thread date parsing by gsd4me

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.