Good point. Leaving aside issues of "What constitutes a word", this process seems like it would boil down to:
sub lcs { my ($string, $find) = @_; $string = join ' ', split ' ', $string; my @f = split ' ', $find; my ($starting_point, $max_length, $substr) = (0,0, ''); foreach my $start ( 0 .. $#f - 1 ) { foreach my $len ( 1 .. $#f - $start - 1 ) { my $search = join ' ', @f[$start .. $start + $len ]; if ( $string =~ $search ) { if ( $len > $max_length ) { $max_length = $len; $start_point = $start; $substr = $search; } } } } return $search; }

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re^5: Finding a LCS module on word level by dragonchild
in thread Finding a LCS module on word level by st_ale

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.