On Thu, 29 Jan 1998 09:53:19 -0700, Dan Ingalls wrote:

>
>2.  We already have a couple of tools that help a lot with the inconvenience
>of matching case during programming.  For one thing, the spelling corrector
>will usually do the job for you.  [You might be interested to know that it
>is easy to change the corrector to take action without even asking if one
>of the alternatives differs only in case].  Also, many people are unaware
>of the cmd-Q feature that will complete a partially typed selector, saving
>time to type the letters as well as to guess at their case.  [If you haven't
>typed enough to be unambiguous, you can keep hittinq cmd-Q to see more
>alternatives.  Also cmd-sh-A (we need a simpler pattern) will step forward
>between keywords so inserted]
>
>3.  One step which would help with the real problem, without any significant
>compatibility issues, would be to recognize and discourage the definition of
>a method whose pattern is equal to an existing pattern in letters but not in case.

It seems to me the best approach would be to provide a tool that lists similarly
named methods.  That would allow case-sensitivity and assist the user in detecting
mis-typed words.

Terry Raymond
Crafted Smalltalk
(401) 846-6573    http://www.craftedsmalltalk.com