OK, I've got two questions.

The first, I'll probably figure out on my own in due time, but the second might be Acatualy Interesting.

Question the first: I've got a bunch of filenames of the form "id.ext". I want to sepperate it into the id part and the extention part. Now, I could do this with a simple split '.', $filename. However, that won't work if the id part contains dots. The way I'm attempting to do it now is with m@^(.*)\.(.*?)$@ (in list context). This doesn't work; it returns the empty list.

The other question is this: Will a regex of the form .*c ever match differently from [^c]*c, and if not, why doesn't the regex parser optimize it to the later form? What if the first was .*?c

Thanks,
James Mastros,
Just Another Perlmonks Novice

In reply to Probably silly regex question / not so silly regex question by theorbtwo

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.