I'm insanely proud of this one as it represents the most interesting bit of coding I've had to do in a while. It even seems to work, although I did cheat by importing POSIX.
#! /usr/bin/perl -w
use strict;
use POSIX qw(ceil);
sub elgon
{
my $string = shift;
my @answers;
my %char_hash = map { $_ => 1} split //, $string;
foreach my $key (keys %char_hash)
{
my @appearances;
for (my $i = 0; $i < length($string); $i++)
{
push (@appearances, $i) if substr($string, $i,
++ 1) eq $key;
}
foreach my $start(@appearances)
{
foreach my $finish(reverse @appearances)
{
next if $start >= $finish;
my $half_length = ceil(($finish - $sta
+rt + 1) / 2);
push @answers, substr($string , ($star
+t) , ($finish - $start + 1) ) if substr($string, $start
, $half_length) eq reverse substr ($string, ($finish - $half_length +
+1), $half_length);
}
}
}
return "FAILED!" if ! scalar(@answers);
my $longest = "";
map { $longest = $_ if length($longest) < length($_) } @answer
+s;
return $longest;
}
|
UPDATE: There may be a minor bug in my use of POSIX, however I may be able to get round this as substr() automagically rounds down fractional values which are passed to it.
UPDATE^2: Fencepost error in ceil() function call fixed.
UPDATE^3: The reason why it fails is that the ordering can sometimes be wrong if there is more than one palindrome in the same string, due to the randomisation as the hash keys are fetched. I'll fix this at some point in the near future...
UPDATE^4: Issue fixed; Was in fact due to boneheadedness on my part. Now should work nicely, although not as pretty as it was.
UPDATE^5: Prettified a bit.
Elgon
"Stercus! Dixit Pooh. Eeyore, missilis lux navigii heffalumporum iaculas. Piglet, mecum ad cellae migratae secundae concurras."
-
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.
|
