From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,768ec7d79291ed2c
X-Google-Attributes: gid103376,public
From: steved@pacifier.com (Steve Doiel)
Subject: Re: IDENTIFIERS in Upper Case
Date: 1997/03/28
Message-ID: <5hfd5b$4ro$1@news.pacifier.com>#1/1
X-Deja-AN: 228905761
References: <1997Mar26.185431.12742@nosc.mil>
 <collins-2703970617290001@ratbert.cs.wm.edu>
Organization: Pacifier BBS, Vancouver, Wa.  ((360) 693-0325)
Newsgroups: comp.lang.ada
Date: 1997-03-28T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <collins-2703970617290001@ratbert.cs.wm.edu>, collins@cs.wm.edu 
says...

>Many reading studies have been done for general text (not programs)
>that all seem to indicate that all uppercase "requires concentrated
>attention and is slow to decipher." (Jan White, _Graphic design for
>the electronic age_) One reason is the monotonous rectangularity of
>uppercase text. Lowercase letters differ from each other in shape
>and so are easier to recognize -- ascenders, descenders, and their
>lack provide distinctive visual patterns. Even the dot over the "i"
>helps to distinguish "i" from "m," "n," and "v" in handwritten text.
>
The keynote address at Tri-Ada 95 shed a lot of light on this subject
for me.  A small part of the subject was pattern recognition.

Take for example the following code

  IF a < b THEN
    DoProc1( arg )
  ELBE
    DoProc2( arg )
  END IF;

You may (or may not) have noticed that I misspelled the word 'ELSE'.  I
occasionally have the compiler catch such a misspelling for me.

Ok.  What's my point?  My point is that when you look at the
construct you don't necessarily read the keywords.  When you see the
structure, particularly if it is consistantly formatted, you recognize
the construct and look directly to the condition for the IF and the
actions taken for each branch.

It's much the same as when you see a stop sign.  You may not actually read
the word "STOP", but rather you recognize the shape of the sign and know
what it is immediately.

It is for this reason that I believe that whatever convention you choose
it should be one that allows as much instant pattern recognition as possible.

The coding convention we use is more elaborate than others I have heard
suggested but conveys more information at a glance.

>
>(P.S. I know That RD just favors a consistent style and is flexible
>      enough to adopt any style. Consistency is good.)
>
>                         Bob Collins, collins@cs.wm.edu
Agreed.

Steve Doiel
steved@pacifier.com