comment on

Having written the exact code once myself, I find it disgusting :P use B::Deparse , then transform the results

$ perl -MO=Deparse -p -i.orig -e "s/foo/bar/; ... "
BEGIN { $^I = ".orig"; }
LINE: while (defined($_ = <ARGV>)) {
    s/foo/bar/;
    die 'Unimplemented';
}
continue {
    die "-p destination: $!\n" unless print $_;
}
-e syntax OK
[download]

into a template

#!/usr/bin/perl --

use strict;
use warnings;
Main( @ARGV );
exit( 0 );
sub Main {
    RuinSomeFilesOrig(@_);
}
sub RuinSomeFilesOrig {
    local *ARGV;
    local $^I = ".orig";
    local @ARGV = @_;

    LINE: while (defined($_ = <ARGV>)) {
        s/foo/bar/;
        ...;
    }
    continue {
        die "-p destination: $!\n" unless print $_;
    }
}
[download]

then turn it into a distribution with scriptdist :D

In reply to Re^2: perl -pi -e s'/^\s+//'g $file by Anonymous Monk
in thread perl -pi -e s'/^\s+//'g $file by david_lyon

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks