Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Are you sure you want hamming-distance instead of a more flexible edit-distance?

Deduplicator
– Deduplicator

2017-08-15 18:03:19 +00:00
Commented Aug 15, 2017 at 18:03
@Deduplicator Nope! Not sure at all! Sounds like the OP should try several different approaches and see which works best =) (Nice spy, by the way.)

Cort Ammon
– Cort Ammon

2017-08-15 18:07:41 +00:00
Commented Aug 15, 2017 at 18:07
Levenshtein distance has worked well for me in the past (Damerau-Levenshtein distance would probably be even better)

Justin
– Justin

2017-08-15 18:14:42 +00:00
Commented Aug 15, 2017 at 18:14
To be honest I already embrace the view that error handling is part of the control flow and not something to be done because it has to be done, hence my quest for the best modern approach

Francesco
– Francesco

2017-08-15 18:49:21 +00:00
Commented Aug 15, 2017 at 18:49

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »