Not something I'd recommend. It's what I did before I found out about soundex and metaphone. However it is a cute regex trick. 
sub offby {
        my($dist,$word,@possibles)=@_;
        my($re)=sprintf(
                q|^%s:%s$|,
                join(q|.?|,map{q|(\w*)|}(0..$dist)),
                join(q|.?|,map{"\\".($_+1)}(0..$dist))
        );
        my(@suggestions);
        #print "user $word regexp $re\n";
        foreach(@possibles) {
                my($str)="$word:$_";
                if($str=~/$re/) {
                        push(@suggestions,$_);
                }
        }
        return(@suggestions)
}

[download]

In reply to Re: Read a column; Compare strings for close (not exact) matches by flogic
in thread Read a column; Compare strings for close (not exact) matches by eyidearie

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.