<#5 - Introduce Explaining Variable

Series Index

#7 - Remove Assignments to Parameters >

sub print_perimeter_and_area{
    my $self = shift;

    my $temp = 2 * ( $self->{_height} + $self->{_width} );
    print "$temp\n";
    $temp = $self->{_height} * $self->{_width};
    print "$temp\n";
}
[download]

sub print_perimeter_and_area{
    my $self = shift;

    my $perimeter = 2 * ( $self->{_height} + $self->{_width} );
    print "$perimeter\n";
    my $area = $self->{_height} * $self->{_width};
    print "$area\n";
}
[download]

Not much of note here, just keep in mind Fowler's exceptions: loop variables or collecting variables are all good. Generally, I don't find loop variables to be all that useful in Perl, and I don't know that I would reuse one anyway. I imagine that Fowler is alluding to something like:

my $i;
for $i ( 1..$some_max ){
   #do something
}

# and later
for $i ( 1..$some_other_max ){
   #do something else
}
[download]

but I don't generally find myself doing that anyway. True, loop variables are rarely going to get you in trouble, as they are usually initialized on each iteration, but it certainly doesn't make the code particularly readable. As such, I'd rather name my loop variables based on what they're actually doing. But I also like $verbose_variable_names, so YMMV.

The upshot is that this refactoring pattern is as much about making your code understandable as it is about avoiding errors that can occur when you reuse a temp variable. If you forget to reinitialize it before the second time you use it (or, say, accidentally delete the line that does), you're in trouble.

perl -e 'split//,q{john hurl, pest caretaker}and(map{print @_[$_]}(joi
+n(q{},map{sprintf(qq{%010u},$_)}(2**2*307*4993,5*101*641*5261,7*59*79
+*36997,13*17*71*45131,3**2*67*89*167*181))=~/\d{2}/g));'
[download]