One of the local roads is I-66, which has the same scansion as Car 54. Much merriment ensues.
There's a scout troop shoirt a child, Khrushchev's due at Idlewild, I-66 where are you -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf of Farley, Peter [00000dc9d8785c29-dmarc-requ...@listserv.uga.edu] Sent: Tuesday, June 27, 2023 2:45 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Conditional assembly variable scope OT Re: "Oooh! Oooh! Oooh!" -- Ah, someone else who remembers Toody and Muldoon . . . "Car 54 Where Are You" 😊 Sorry, I could not resist - I needed a laugh today. Peter -----Original Message----- From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On Behalf Of Paul Gilmartin Sent: Tuesday, June 27, 2023 2:34 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Conditional assembly variable scope On 6/27/23 12:17:21, Seymour J Metz wrote: > No. If you have a business case, maybe an RFE for name spaces. Oooh! Oooh! Oooh! Also for label symbols as well as conditional symbols, freeing the programmer of the burden of using distinct component prefixes in data area definitions. It could mesh well with labelled USING. FAP did this with the HE[A]D pseudo-op. > ________________________________________ > From: Paul Gilmartin > > Is there a way to declare a symbol in a macro so that it is visible in > the declaring macro and in macros it calls but not in open code nor in > macros calling the declaring macro? > > That would mimic the customary behavior of static scope in block > structured languages and POSIX shell "export", but not quite REXX > "PROCEDURE EXPOSE".. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.