On 12/30/2011 7:33 AM, Edward Jaffe wrote:
On 12/30/2011 6:43 AM, John Gilmore wrote:
Case control is a more complicated issue. In situations like the one
EJ describes I have found the two options that the HLASM already
supports, viz.,
o CASE | NOCASE, and
o MACROCASE|NOMACROCASE
entirely adequate; but this is because I work in a very small group of
usually two and never more than three people in which my taste is, if
not controlling, very influential.
Honestly, I forgot about these options. Thanks for reminding me. I will see if
they meet my needs.
OK. I reviewed these options. They do NOT do what I need. (This is probably why
I forgot about them.)
1. COMPAT(CASE) enforces a requirement for uppercase opcodes and symbols. Almost
exactly the opposite of what I want.
2. COMPAT(MACROCASE) converts macro operands to uppercase.
I'm not interested in a COMPAT() option to remain compatible with older
assemblers. I want a new option, as described previously, to generate a
diagnostic when a programmer references MyField as (for example) MyfiEld. For
ease of transition, it might be nice if the option could be limited to certain
symbols or sections. For example, a new operand on the DSECT statement that says
the fields defined herein must be referenced using the correct case.
--
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/
