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=0.1 required=5.0 tests=BAYES_05,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: mfb@mbunix.mitre.org (Michael F Brenner)
Subject: Re: IDENTIFIERS in Upper Case
Date: 1997/03/27
Message-ID: <5hdnih$g1d@top.mitre.org>#1/1
X-Deja-AN: 228714323
References: <1997Mar26.185431.12742@nosc.mil>
Organization: The MITRE Corporation
Newsgroups: comp.lang.ada
Date: 1997-03-27T00:00:00+00:00
List-Id: <comp.lang.ada>


The worst capitalization scheme is one that involves the programmers
instead of doing it automatically with tools. The second worst is any
capitalization scheme that introduces capital letters to identifiers
or keywords. The correct scheme is to use a typesetting tool to 
emphasize the assertions (preconditions, invariants, and postconditions),
and de-emphasize the identifiers and keywords. An exception is that,
during debugging or during expository text, the typesetting tools 
should be set to give various colors to what you are currently 
describing. For example, in solving the year 2000 problem, the
typesetting tool should color all inter-chip messages containing
2-digit year fields in red, should capitalize all uses of the word
NEW, should color all date processing logig using the Zeller congruence
in blue, and should italicize all preconditions involving date
calculations. When people in authority have personal stylistic
preferences for capitalization, they should identify them as
personal preferences, and not as software engineering. It takes
time to for humans to carry out those preferences, which impacts
the amount of time it takes to change software and to analyze
the impact of those changes.