Yep. I guess it's not really a spell checker. It compares two words to figure out how close they are in spelling so I suppose a spell checker might use it to suggest correct spellings from a dictionary having detected a misspelled word. Download setlocals from http://www.lcsql.com/free-stuff.html. In the main stack script, you'll find two handlers: OptimalStringDistance and DamerauLevenshteinDIstance. I found OptimalStringDistance to be the best fit for this application but the other one works too.
On Thu, Sep 3, 2015 at 9:13 AM Richard Gaskin <ambassa...@fourthworld.com> wrote: > Peter Haworth wrote: > > > On Wed, Sep 2, 2015, 7:38 PM Mark Wiederwrote: > > > >> The tl;dr is that by letting an algorithm declare variables instead > >> of doing the work of finding the missing ones manually you're > >> actually compounding the problem. It makes it harder to spot the > >> accidental errors at runtime. > >> > >> If you are editing a script and type 'tVar' instead of 'tVar1' you'll > >> have a hard time finding the error after tVar1 is legitimized. > >> > > The spell check algorithm catches that. > > Got one handy? > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
