With all these cool responses, it is clear I needed to write myself a palindrome checker. So here goes.

#!/usr/bin/perl -w

use warnings;
use strict;

my $text;
for my $file (@ARGV) {
  {
    local $/=undef;
    open my $fh, '<', $file or die;
    $text = <$fh>;
    close $fh;
  }
  $text =~ s/\s//g;

  if ($ENV{'debug'}) {
    print "forwards  = $text\n";
    print "backwards = " . reverse($text) . "\n";
  }

  if ($text eq reverse $text) {
    print "$file: Palindome OK.\n";
  }
  else {
    print "$file: NOT a palindrome.\n";
  }
}
exit 0;

[download]

This didn't seem worthy of a separate Cool Uses for Perl posting.

EDIT: Fixed based on JavaFan's comments. I no longer split the text and flip it to compare, and I do a string "is equal" compare instead of re match.

In reply to Re: JAPH palindrome. by jffry
in thread JAPH palindrome. by jffry

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.