On 8/28/25 02:20, Jonathan Scott wrote:
HLASM itself contains a lot of mixed-case assembler source, and the HLASM
operating system interfaces for MVS, CMS and Linux are mostly written in
mixed-case PL/X. There are indeed some limitations on macro keyword values,
but an increasing proportion of macros have been coded or modified to support
lower case values.
...
I consider MACROCASE to be a design blunder. For all
other options, COMPAT(option) provides behavior compatible
with Assembler H; COMPAT(NO option) provides incompatible
behavior. However, for the *SAME* source code,
COMPAT(MACROCASE) provides incompatible behavior; for
compatible behavior, COMPAT(NOMACROCASE) is necessary.
Data type CU is Unicode, which has nothing to do with upper case. A macro can
convert a string to upper case using the UPPER built-in function.
...
How does that work? can I code something as simple as:
DC CU'π' and get the value of x'cf80' for CCSID 1209?
--
Thanks,
gil
