9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Elliott Hughes Elliott.Hughes@genedata.com
Subject: [9fans] Brian Kernighan?
Date: Thu, 11 Nov 1999 11:56:05 +0100	[thread overview]
Message-ID: <19991111105605.ZvNMk1khc8_Q2HthEgYNh9fmQcNEOq6px7trgE-sN-k@z> (raw)

forsyth wrote:
> the Cornell PL/1 compiler used a similar approach to
> do spelling correction on keywords as part of a broader
> attempt to repair all obvious errors in the given program; the results
> were amusing if not enlightening, as they so often are with AI.

IBM's jikes Java compiler also tries spelling correction, but its
ideas of proximity have nothing to do with any human's. it's
particularly unfortunate that it doesn't even know about the
Java naming conventions. (not that i necessarily think it should,
it's just that if it's going to try to guess what you meant to type,
it would be better off making educated guesses.)

there's a big difference between correcting simple typos and
more complicated "wrong identifier" errors.

anyway, back to the point: the original questioner might be
interested in "Finding Approximate Matches in Large Lexicons"
by Justin Zobel (jz@cs.rmit.oz.au) and Philip Dart (philip@cs.mu.oz.au),
which was the best paper i found when trying to come up with
decent guesses in a "dict"-like program.

btw, has anyone had better luck than i at getting information
about the CD-ROM version of the OED, with a view to having
a Plan 9/Unix OED "dict"? ever since i read the acme paper
with its "futtock" example, i've been jealous.

--
"As the Chinese say, 1001 words is worth more than a picture."
	-- John McCarthy





             reply	other threads:[~1999-11-11 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-11 10:56 Elliott [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-11-11 11:16 forsyth
1999-11-11 11:10 Lucio
1999-11-11 10:16 forsyth
1999-11-11  9:43 Lucio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19991111105605.ZvNMk1khc8_Q2HthEgYNh9fmQcNEOq6px7trgE-sN-k@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).