Another safeguard would be to specify that the substitution may happen only once per file. Assuming there is at least one appearance of a version string in the file, and most likely, it's near the very top of the file, that should work and protect you reasonably well.

I'm thinking that the easiest way to achieve that is to simply slurp the whole file, and process it with a single s///. Source files are usually short enough to not pose any problems. According to perlrun you can use the -0777 switch to slurp the whole file (that's a zero, not a capital O, BTW. I always make that mistake.)

In reply to Re^2: Modifying File Contents by bart
in thread Modifying File Contents by ramthen

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.