On Mon, Oct 27, 2008 at 20:28, Rob Dixon <[EMAIL PROTECTED]> wrote:
> John W. Krahn wrote:
>>
>> The fewer lines of code to read and/or write, the easier it is to spot
>> mistakes, the less chance for "action at a distance."
>
> Not at all.
>
> Is this
>
> sub wanted { return unless -f; open my $FH, '<', $_ or die "Cannot open '$_'
> $!"; while ( <$FH> ) { /\Q$string/ && print $REPORT "$File::Find::name\n" and
> return; } } find \&wanted, '/test';
>
> easier to debug?No, it is not, but it also isn't fewer lines of code; it is many lines of code compressed into fewer lines. Fewer lines of code means using higher level constructs (such as anonymous subroutines) to eliminate redundant code. -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
