Lady_Aleena,
This is also an example of why writing modules to store commonly used code is far better than copy/paste strategies. I know it seems silly to write a function just to perform s/\.pl$// but if it had been, you could have fixed it once and all of the other code that used it (even the code you didn't remember writing) would have been fixed as well.

Regarding the humorous results of incorrect regexes - yes. I was writing a code that used OCR to parse bibiliographies from academic papers in the form of a PDF. I don't remember the exact details but due to the imperfect OCR process - there were a few journals that I would like to subscribe to if they were real ;-)

Cheers - L~R

In reply to Re: Writing regexes, think ahead just a bit. by Limbic~Region
in thread Writing regexes, think ahead just a bit. by Lady_Aleena

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.