We code:
MACRO
FOO &BAR,&TEXT=
&uBAR SETC (UPPER '&BAR')
AIF ('&uBAR' EQ 'BLAH').label
so invokers can specify keywords in any case and macro will be properly
recognized it. Actual data (e.g. &TEXT) may remain mixed case for
processing.
Robert Ngan
CSC financial Services Group
From: Paul Gilmartin <[email protected]>
To: [email protected]
Date: 2011/12/31 10:11
Subject: Re: mixed case in assembler
Sent by: IBM Mainframe Assembler List <[email protected]>
On Dec 30, 2011, at 08:33, Edward Jaffe wrote:
>>
>> o CASE | NOCASE, and
>>
>> o MACROCASE|NOMACROCASE
>
> Honestly, I forgot about these options. Thanks for reminding me. I will
see if
> they meet my needs.
>
Does IBM guarantee that any macros it distributes will work
correctly regardless of customers' setting of these options,
or will IBM require that customers use certain settings?
What about ISVs?
Will macros be tested under all combination of these settings?
This is a nightmare for ISVs; some people suspect that IBM
itself tests largely the PL/S branch and leaves testing of
the assembler branch to customers.
We did well enough for 40 years with case-sensitive assemblers.
The misguided attempt to add case-insensitivity causes chaos
and instability.
-- gil
