Closures are cool, but I dont really see any practical or theoretical benefit to what you are tutoring:
package Max;
sub new {
my $class = shift;
my $max = undef;
return bless \$max, $class;
}
sub compare{
return $_[1] > $_[2];
}
sub max{
my $self = shift;
for ( @_ ) {
$$self = $_ if $$self == undef || $self->compare($_, $$self);
}
return $$self;
}
package StringMax; our @ISA = ('Max');
sub compare {
return length($_[1]) > length($_[2]);
}
package main;
my $max= new StringMax();
while ( <FH> ) {
chomp;
$max->max($_);
}
my $long_str = $max->max();
The same functions, the same number of lines - better organized for applying to real problems.
time was, I could move my arms like a bird and...
-
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.
|