An old trick: write the instructions first. Make them clear, easy to get it 
right, hard to screw up. 

Then write the code to implement the instructions as written. 

There may be some perceived technical need for null, splat, blank, or no value 
at all, but the difficulty in trying to explain to the poor user may overshadow 
the technical issues. 

 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Phil Smith
Sent: Monday, March 19, 2012 4:13 PM
To: IBM-MAIN@bama.ua.edu
Subject: Theology question

In our configuration data set, you can specify a default, global value for 
something. Specific entries in the configuration can override that global 
value. However, there are cases where you *must* specify a null value on a 
specific entry, as if you had no default, global value.

Our internal debate is over whether an asterisk is appropriate to say "No, 
really, don't use any value here".

So examples might be:

thing1(option1,option2)  /* This defines a thing with an explicit option1 and 
explicit option2 */

thing2(option1)  /* This defines another thing and says "use the default, 
global value for option2 if you have one" */

thing3(option1,*)  /* This would define another thing and say "even if you have 
a default, global value for option2, pretend you don't" */

thing4(option1,'')  /* This is an alternative form of thing3 */

One of us feels that the asterisk should mean "use the global default". One of 
us feels that the double quote is ugly and error-prone.

Based on the collective wisdom of the centuries, what *feels* right to you?
--
...phsiii

Phil Smith III
p...@voltage.com<mailto:p...@voltage.com>
Voltage Security, Inc.
www.voltage.com<http://www.voltage.com>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Reply via email to