G'day TJCooper,

Here's one way you might go about this: 

#!/usr/bin/env perl -l

use strict;
use warnings;
use autodie;

my $highest = 0;
my $re = qr{pm_1069813_results(\d+)\.txt};
opendir my $dh, '.';
map { /$re/ and $1 > $highest and $highest = $1 } readdir $dh;
closedir $dh;
my $next_file = 'pm_1069813_results' . ++$highest . '.txt';

print "Next file: $next_file";

[download]

Output:

Next file: pm_1069813_results4.txt

[download]

Current files:

$ ls -1 pm_1069813_results*.txt
pm_1069813_results1.txt
pm_1069813_results2.txt
pm_1069813_results3.txt

[download]

-- Ken

In reply to Re: Sequentially numbering output files rather than overwriting an existing file by kcott
in thread Sequentially numbering output files rather than overwriting an existing file by TJCooper

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.