If you go over the entire list for every word, it's just going to take a lot of time. You want a hash instead.

#!/usr/bin/perl

use strict;
use warnings;

# the diamond operator is special:
# supply filenames on commandline or provide input on STDIN and it jus
+t works

my @word = <>;
chomp @word;

my %in_list;
undef @in_list{ @word }; # now all entries from @word are keys in %in_
+list

for( @word ) {
    my @hook = grep { exists $in_list{ $_ } } (
        substr( $_, 1 ),
        substr( $_, 0, length( $_ ) - 1 ),
    );
    print "$_: @hook\n" if @hook;
}

[download]

You go through the list of words, generating front and tail hooks for each, and then look up whether there such a key exists in the hash.

Makeshifts last the longest.

In reply to Re: speedier text matching by Aristotle
in thread speedier text matching by lemnar

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.