Re: Controlling Running Perl Scripts

maybe something like ...?


our @sequence = ( "path1",
                  "path2",
                  # ...
                );

sub nextpath {
    for ( my $i=0; $i<=$#sequence; $i++ ) {
        ( $PATH_INFO eq $sequence[$i] ) or next;
        ( $i < $#sequence )
            ? return( $sequence[$i+1]);
            : return( $sequence[0]);
    }
    undef();
}
[download]

(updated with thx to shigetsu)

__________________________________________________________________________________

^M Free your mind!

Comment on Re: Controlling Running Perl Scripts Download Code

Replies are listed 'Best First'.
Re^2: Controlling Running Perl Scripts by shigetsu (Hermit) on Apr 25, 2007 at 16:12 UTC
There's a minor typo: `our $sequence = ( "path1", "path2", # ... );` [download] should probably read `our @sequence = ...` [download] instead.	[reply] [d/l] [select]
Re^3: Controlling Running Perl Scripts by Anonymous Monk on Apr 25, 2007 at 17:47 UTC
I am going to test with something like that!Thanks!	[reply]
Re^4: Controlling Running Perl Scripts by suaveant (Parson) on Apr 25, 2007 at 18:29 UTC
Of course, modularize it so you can easily share it across all your scripts... if you only have one sequence then an array works... if you have multiple or may have multiple then I would either use files or a hash of arrays and pass the hash key or the file name between the CGIs that contains the proper sequence. - Ant - Some of my best work - (1 2 3)	[reply]