On 1/1/2012 7:42 PM, Tony Harminc wrote:
On 30 December 2011 10:29, Edward Jaffe<[email protected]> wrote:
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! ;-)
That sounds like something to be enforced by either the global xref
program that every development shop has, or perhaps by some stage of
the SCCS check-in process.
We don't have that global XREF program! Lol!
Consider the following:
EZDrm DSECT ,
EZDrmEyeCatch DS CL4
.
. (other fields for EZDrm)
The most obvious solution is a SYMCASE(ANY|ASIS) assembler option that, like
most options, would affect the entire assembly. There would be ACONTROL support
to handle exceptions--for example references made from inside IBM or other
providers' macros you cannot change.
With the default of SYMCASE(ANY), the assembler would work as it does today
i.e., allow any case when referencing EZDrmEyeCatch such as EzDRMEYeCaTCh. But,
with SYMCASE(ASIS), symbols would need to be specified exactly as they are
defined or an informational or warning diagnostic would be produced.
--
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/
