That Perl smells a little like Java.
For example, for some of those smaller functions, I'd do this:
sub gene_length {
my @gls = sort map { length } keys %genome;
die "Invalid genotype" unless $gls[0] == $gls[$#gls];
return $gls[0];
}
And this:
use List::Util 'first';
sub check_for_winner {
return first { get_result($_) == $target } @population
}
And this;
use List::Util 'sum';
sub get_population_fitness_score {
return sum map { get_fitness_score($_) } @population;
}
(Or just inline those statements, if they're only used once.)
In other words, when you can trim it down so that you can actually tell what it's doing at a glance, then it's easier to benchmark!.
-
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.
|