It would always be a good idea to enable strict and warnings.

From looking at the tests it looks like parse returns a true/false value depending on parse success/failure, and not the actual date(s).

$ perl -l use strict; use warnings; use Date::Manip; my $obj = new Date::Manip::Recur; my $err = $obj->parse( qw(1:2:3:4*12:30:00 2000010500:00:00 2000010100:00:00 2003010100:00:00 ) ); die $obj->err() if $err; my @dates = $obj->dates(); foreach my $date (@dates) { print $date->value; } __END__ 200015123000 2001330123000 2002624123000 $
--
No matter how great and destructive your problems may seem now, remember, you've probably only seen the tip of them. [1]

In reply to Re: Date::Manip::Recur is not returning a list by andreas1234567
in thread Date::Manip::Recur is not returning a list by desertrat

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.