On 12/30/2011 12:34 AM, Edward Jaffe wrote:
On 12/23/2011 8:42 AM, Steve Comstock wrote:

Sure, camel case. And the nice thing is the Assembler
will recognize variable names if you happen to forget
and not capitalize the first letter, since it is
case-insensitive.

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.

But, to each his own.



--
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/



--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
    for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

Reply via email to