in reply to Re: Changing every subroutine in many perl scripts
in thread Changing every subroutine in many perl scripts

Should I use PPI::Transform to edit the subroutines?

From the CPAN page, I got that I could do something like this:

my $transform = PPI::Transform->new(
    param1 => 'value1',
    param2 => 'value2',
);

# Change a file in place
$transform->file( 'Change.pm' );

[download]

But I don't understand what are the params and values when creating the new transform object.

Replies are listed 'Best First'.
Re^3: Changing every subroutine in many perl scripts
by nitin1704 (Sexton) on Jul 25, 2012 at 04:17 UTC

    Okay, I got it now, after going through the CPAN documentation a bit more.

    
use strict;
use warnings;
use PPI;

my $file = '/path/to/perl/script.pl';
my $Document = PPI::Document->new($file) or die "oops";

for my $sub ( @{ $Document->find('PPI::Statement::Sub') || [] } ) {
    unless ( $sub->forward ) {
        my @elements = $sub->children;

        for ( my $i = 0 ; $i < @elements ; $i++ ) {
            if ( ref $elements[$i] eq "PPI::Structure::Block" ) {
                $elements[$i]->start->add_content("my mars code");
            }
        }
    }
}

$Document->save($file.".new");

    [download]
[reply]
[d/l]

      The loop would be better written:

      for my $sub (@{$Document->find('PPI::Statement::Sub') || []}) {
    next if $sub->forward;

    for my $child ($sub->children) {
        if (ref $child eq "PPI::Structure::Block") {
            $child->start->add_content("my mars code");
        }
    }
}

      [download]

      The next if ... saves a level of indentation and is easier to understand (at least for me) than an unless.

      Using a Perl style for loop in place of the C style for loop is easier to read, easier to understand, more compact and much less likely to get wrong.

      True laziness is hard work
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom