Gary Weinhold wrote: >I can imagine a junior assembler programmer thinking that they should >branch to the DROP to ensure it was executed before entering the >following code. I think it takes a while for new programmers to >understand what USING and DROP statements actually do other than the >necessity of having a USING at the beginning of a program (often >hidden in a macro).
Indeed! Addressability is a tricky thing to really grok. I have a fond memory of (gulp) over 40 years ago being asked to add some stuff to EXEC 2 on VM/370 R6. It immediately blew addressability, and my then-manager said "Ehhh, maybe let's not". I said, "Let me do it and I'll come out of it understanding addressability". And he did, and I did! (Well, at least somewhat--I'll not claim to Know All, that would be obnoxious.) For me, the operative question on this is, "Is there a use case where this would make sense to do?" and I do not believe that there is one. What's the saying about "Just because you can doesn't mean you should"? Plus I've never accepted any RC other than 0 as acceptable from an assembler job. Have you?? ...phsiii ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
