I am envious of John Gilmore. He must have a far better memory than do I.
To me, this comes down to readability, as that, in my opinion,is the most
important legacy that a coder can leave for those who follow him/her in
trying to deal with a module.
Consider an example where my macro accepts
Thus I agree completely with EJ. You are not overly concerned about someone
reading what command you entered (as they would likely be doing so only if
analyzing a dump or trying to figure out what command was actually
entered that did something you did not appreciate). But you should be
Code should ideally be self-commenting as otherwise the comments get
stale. So adding one saying C here really means CANCEL might be a benign
version of that but it's still subject to becoming wrong.
Cheers, Martin
Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Banking
On 2014-07-28, at 23:17, Ed Jaffe wrote:
CANCEL J(1234)
or:
C J(1234)
My preference in documentation tends toward using the shortest possible
command and operand abbreviations in any examples, but I can see both sides...
I deliberately chose an extreme example. I doubt that
All of the comments on and objections to the use of CIDTs of
keyword-parameter values were interesting, and some of them were
drôle.
The notion that coding say action=C instead of action=cancel is
justified|justifiable if a comment explaining that C really means
CANCEL is provided is, I think,
Many years ago, I was initially perplexed by the OS commands and their
abbreviations. A lot of them were abbreviated to their initial letter
S start
R reply
C cancel
D display
L log
M mount
U unload
V vary
W
John Gilmore stated:
Worse, attempts to dispense with such documentation are ill-advised.
COBOL is the notorious example of an attempt to make a programming
language self-documenting. The attempt failed abjectly, with
pernicious side effects because prolixity was misidentified with
clarity.
I
I imagine a more fanciful set of rules was responsible for the single-letter
abbreviations of the system commands.
P is the last letter of STOP; it's where it stops and the p sound is
distinct...
The e sound is emphasized in RESET and since REPLY is more frequently used,
it makes sense to use
On 7/29/2014 11:09 AM, Hall, Keven wrote:
I imagine a more fanciful set of rules was responsible for the single-letter
abbreviations of the system commands.
P is the last letter of STOP; it's where it stops and the p sound is
distinct...
Haha. Or, simply working forward alphabetically, 'S'
