| Subject: | tiny typo in Approx.pm |
| Date: | Wed, 30 Dec 2009 14:37:43 -0500 |
| To: | bug-String-Approx [...] rt.cpan.org |
| From: | jpl [...] research.att.com (John P. Linderman) |
Hi, Jarrko, I hope all is going well. Happy New Year!
I was casting about for an edit distance that included
transposition as a edit operation, and (re-)ran across
String-Approx. There's what I am pretty sure is a typo
in the documentation: I could find no trace of a
Strings::Approx module, so I am assuming the plural
form of String was unintended. A diff against what
I believe was intended follows. -- jpl
diff -p Approx.pm.orig Approx.pm
*** Approx.pm.orig Wed Dec 30 14:27:21 2009
--- Approx.pm Wed Dec 30 14:30:16 2009
*************** The edit distance of "lead" and "gold" i
*** 542,548 ****
B<String::Approx uses the Levenshtein edit distance (tLed) as its
measure, but String::Approx is not well-suited for comparing the tLeds
of strings, in other words, if you want a "fuzzy eq", see above.
! Strings::Approx is more like regular expressions or index(), it finds
substrings that are close matches.>
=head1 MATCH
--- 542,548 ----
B<String::Approx uses the Levenshtein edit distance (tLed) as its
measure, but String::Approx is not well-suited for comparing the tLeds
of strings, in other words, if you want a "fuzzy eq", see above.
! String::Approx is more like regular expressions or index(), it finds
substrings that are close matches.>
=head1 MATCH