Are you sure it's failing? And not just giving what you asked of it, but not expected?

If I run the code you provided, with the string you provided ("P1D"), the match suceeds, and I get this in @temp: 


  DB<1> x @temp
0  undef
1  'P'
2  undef
3  undef
4  undef
5  1
6  undef
7  undef
8  undef

[download]
To me that looks like what you should be getting, given the approach you've chosen - each field in the grammar will always come into the same array field.

Could it be that you saw that first undef and didn't realize that the data was in the later fields?

With the approch you're using, when the regexp doesn't match, you will get an empty array, so test for that. (Maybe by looking at $#temp).

In reply to Re: regex - parsing a string with many optional fields by matija
in thread regex - parsing a string with many optional fields by Anonymous Monk

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.