Path: utzoo!mnetor!uunet!husc6!think!ames!pacbell!att-ih!ihnp4!inuxc!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!osiris.cso.uiuc.edu!goldfain
From: goldfain@osiris.cso.uiuc.edu
Newsgroups: comp.lang.smalltalk
Subject: Re: embeddedCapitals
Message-ID: <12100008@osiris.cso.uiuc.edu>
Date: 23 Mar 88 06:11:00 GMT
References: <2472@pdn.UUCP>
Lines: 15
Nf-ID: #R:pdn.UUCP:2472:osiris.cso.uiuc.edu:12100008:000:789
Nf-From: osiris.cso.uiuc.edu!goldfain    Mar 23 00:11:00 1988


Now that I've thought about it for a bit, I think there is no  solution to the
embedded-capitals-causes-naming-errors problem.  Anything   you do to  improve
readability will cause possible   name-matching  errors, whether you  separate
parts of long names with spaces, underscores, capitals, etc.

On the other hand, if you do not put any of these in, there will be a  loss of
readability, which can result in different kinds of errors.

I think everyone just has to deal with this tradeoff however they prefer.

One thing  that certainly  does help, as  Prof. Johnson  noted,  is  an active
checker with   spelling-correction suggestions whenever  a name  is undefined.
This has caught and easily corrected every capitalization error I can remember
making when programming in Smalltalk.