One of the obvious problems is, that you want to use slashes inside your regex without escaping them.

/ --> \/

If I where you I'd change delimiter and try m{REGEX} instead of m/REGEX/ .

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

update

there where more issues, but this works for me ( perl -dE0 starts the debugger )

  DB<25> @m =  qw{01/LC-13/E10GbE-1 01/LC-13/E10GbE-1,01/LC-14/E10GbE-
+1}

  DB<26> say join ":", m{\d\d/\w+-(\d+)/\w+-(\d+),?}g for @m
13:1
13:1:14:1

  DB<27>

[download]

update

If the snippets don't always start with \d\d change it to \d+

If I where you I'd consider spliting on , and then / .

Then applying a simple regex, should be more stable and maintainable.

In reply to Re: Problem with regexp to match by LanX
in thread Problem with regexp to match by logangha

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.