Charles, all, That type of error also occurs within HLASM when it is processing macro code. some errors are caught only if the pertinent statement is actually executed. It hit me so many times that we implemented a non-compatible feature in z390 to do a better job at early error detection. I have liked using that feature very much.
Kind regards & happy programming! Abe === Op 01/05/2024 om 20:17 schreef Charles Mills: > Well, and it is a feature of interpretive execution. When you branch to a > label, it looks until it finds that label. It doesn't keep looking to see if > there is another. (Yes, it could and might, but it would take time, and it > doesn't.) > > It's an example of something I dislike about both Rexx and Python: errors > that would be caught in compilation in other languages are not caught until > you hit them, perhaps at oh-dark-thirty at a customer site. > > Charles > > > -----Original Message----- > From: IBM Mainframe Assembler List [mailto:[email protected]] > On Behalf Of Phil Smith III > Sent: Wednesday, May 1, 2024 10:00 AM > To: [email protected] > Subject: Re: ASMA043E Previously defined symbol > > Paul Gilmartin wrote, re Rexx being fine with duplicate labels: >> That's bad. > That's WAD. Remember, the goal of Rexx was ease of use. Just sayin'.
