|"Near Miss" error handling? email@example.com (2001-03-27)|
|Sv: "Near Miss" error handling? firstname.lastname@example.org (srs srs) (2001-03-31)|
|Re: "Near Miss" error handling? email@example.com (Joachim Durchholz) (2001-04-04)|
|Sv: "Near Miss" error handling? firstname.lastname@example.org (srs srs) (2001-04-10)|
|Re: "Near Miss" error handling? email@example.com (2001-04-14)|
|Re: Sv: "Near Miss" error handling? firstname.lastname@example.org (Ben Pfaff) (2001-04-15)|
|Re: "Near Miss" error handling? email@example.com (2001-04-15)|
|Re: "Near Miss" error handling? firstname.lastname@example.org (2001-04-16)|
|Re: "Near Miss" error handling? email@example.com (Christian Lindig) (2001-04-16)|
|From:||"srs srs" <firstname.lastname@example.org>|
|Date:||10 Apr 2001 01:46:54 -0400|
|References:||01-03-135 01-03-171 01-04-012|
|Posted-Date:||10 Apr 2001 01:46:54 EDT|
"Joachim Durchholz" <email@example.com> skrev i en meddelelse
> Note that Soundex is tied to the English language. Applying it to words
> in any other language produces utter nonsense.
I think most programmers, regardless of their native language, use English
identifier names. Not all, but most. Besides, variants for other languages
do exist; see SpellCheck from TeraTech, for instance.
> The other point is, if it's mistyped identifiers, you probably don't
> want Soundex anyway. Soundex is useful if you want to identify names
> that were misheard, which errors in programming are (usually) mistyped,
> with totally different error characteristics.
> Typical typos are omitted, transposed, or inserted characters. Typical
> "hearos" are wrong vowels and partly omitted syllables.
Soundex empirically works pretty well for typos (omitted, transposed, etc),
but I'm sure it would need adjustments to be optimal (within its limits) for
identifiers, which have other characteristics than people's names.
Another point is that the number of symbols you have to choose from when
suggesting an alternative gets very limited as you only need to check for
identifers within the scope at hand; be it a module, class, function, etc
(except for external references.)
- Stein Roger
Return to the
Search the comp.compilers archives again.