This feels like a job for pi!

bash$  perl -pi .oops -e 's/(\d+)/$1+1/e' filename.ext

[download]

Just what are p, i, and e? Check the perlrun page for further information.

Garh!! davidrw seems to have beaten me by several seconds on this. In answer to his question:

I would say the longer self contained version is probably more maintainable — depending on where the application is used/stored. The pi-way is fine for a one time addition to one's own crontab, but for full platform compatability and for the sake of future readers (who may not know perl all that well), the longer version may be better. It depends.

-Paul

In reply to Re: File I/O by jettero
in thread File I/O by Anonymous Monk

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.