Since you used [.\w]+ to try to match the last file name component, the match will fail if the user supplied a string ending with the directory delimiter (\home\me\foo\bar\).

This takes you beyond just fixing your regex, but if you use the File::Spec module, you can accomodate end-cases like this and get portability to boot. For your example, this might look like:
$pat = File::Spec->catfile($HomePath, ''); if ($Model =~ m/^\Q$pat\E/i) { (undef,$WorkingDirectory,undef) = File::Spec->splitpath($'); } else { # whatever to do if the supplied variable isn't under $HomePath }
The initial File::Spec->catfile call appends a trailing '\' so that it doesn't show up as an initial '\' in the resulting $' that you pass to File::Spec->splitpath.

In reply to Re: Regex Improvement by knight
in thread Regex Improvement by Lexicon

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.