If you want to find palindromes, why not do it with a regex directly?
#!/usr/bin/perl
use strict;
use warnings;
my $str = do {local $/; <DATA>};
$str =~ s/\s+//g;
while ( $str =~ m/( (..+) .? (??{ reverse $2 }) )/xgc )
{
print pos( $str ) . ": $1\n";
pos( $str ) = $-[0] + 1; # slide pos back to the left
}
prints:
14: AGGGA
21: TACAT
25: GTTG
55: GAAAAAAAG
...etc...
I'm not sure how it would compare with the two-stage approach for speed, though. It is much faster if you minimize the qualifier ..+?, but then you end up with the shortest palindrome at each position, rather than the longest.
I make the assumption that you don't care about palindromes shorter than 4 characters. If you bump that upwards, things get faster.
Update: I tested, and it looks like the substr approach is considerably faster, particularly if you do it in a single pass.
-
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.
|