On Dec 30, 2011, at 00:34, 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. > One thing I like to do is to use lower case words in comments and capitalize those words when used as identifiers in code. So I can find only the code with a case-sensitive search in an editor, and both code and comments with a case-insensitive search. This works best if the language enforces consistency in identifiers.
BTW, can ISPF be profiled to do case-sensitive searches by default to spare me a few keystrokes in "f c'String'"? -- gil
