On 5/1/24 09:53:45, Willy Jensen wrote:
REXX is fine with the same label occurring multiple times, it just picks the first. .
That's bad.
-----Oprindelig meddelelse----- Fra: Charles Mills Sendt: 1. maj 2024 17:47 I don't think that anyone has mentioned this point but I think that all languages with which I am familiar (and that support data declarations of some sort) behave the same way. COBOL, C, etc. -- all prohibit duplicate (truly duplicate, after qualification) labels, referenced or not. .
There's static scoping to within blocks. I have used a language which restricted the scope of macros to blocks.
Rexx does not declare variables, so X = 3; X = 4 is not a conflict, just a reassignment. What about Rexx procedure labels? Does Rexx object to
The desire to accept redefinition with identical value appears to arise from undisciplined design and use of header files. But we had a register equates macro that came to conflict with IATYREGS when we added JES3 support. Many JES3 headers used IATYREGS conditioned on setting ofa GBLB. My suggestion either to condition our header likewise, or simply to rely on IATYREGS was rejected. -- gil
