On 12/30/2011 5:23 AM, Steve Comstock wrote:
On 12/30/2011 12:34 AM, Edward Jaffe wrote:
I also like camel case. It looks much better than using underscores to separate
uppercase words. However, I don't consider the assembler's current behavior to
be 'nice'. For example, I will painstakingly plan and create camel case fields
in a control block and then later see code referencing those fields using the
wrong case (due to typos, dyslexia, or what have you). Sometimes those
'misspelled' references get propagated to other code and things really start to
get ugly. I wish there was a way to tell the assembler to be case sensitive.
But words with the same string of letters but different case
are _not_ misspellings. They are the same word, so they
reference the same variables. Using the 'wrong case' just
means using the case preferred by the coder: they are still
the same variables. I consider it 'nice' because each coder
can use the case pattern they prefer and yet everyone is
referencing the same variable: these are not typos.
When I have pointed these issues out, the programmers have acknowledged that
they ARE typos!
The current behavior is fine for those who like it. I would like an option to
enforce case matching.
For example, if I create a field called EZDrmStringsUpper and some developer
codes it as EZDrmStringSupper I would like to have the assembler generate a
diagnostic. Our products support uppercase strings; but we don't feed them
supper! ;-)
But, to each his own.
This is anarchy--exactly what I want to avoid. For our environment, I want the
designer of the control block field to choose the name by which it will be
referenced by other programmers.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
310-338-0400 x318
[email protected]
http://www.phoenixsoftware.com/
