In a recent note, Jeffrey D. Smith said: > Date: Sat, 18 Nov 2006 20:21:32 -0700 > > The flat namespace of HLASM is the real problem. There should be > a way to hide labels within a DSECT until the DSECT is anchored > with a USING. Until the owning DSECT is made addressable through > a USING, the symbol should not conflict with the same name of a > symbol defined in another DSECT. If more than one symbol of the > same name (in different addressable DSECTs), then issue an error > message. Otherwise, just use the symbol that is addressable. There > should be some syntactical sugar that indicates the programmer > knows there are multiple symbol matches and knows the consequences > of using the wrong symbol. > I pretty much agree, though I'm somewhat uncomfortable with further overloading USING. It's bursting at the seams with labelled and dependent USINGs. And how would this work with the new-fangled baseless code, particularly in the case discussed recently where code from two different sources is merged with an editor or with COPY? And remember that the first operand of USING is not necessarily a DSECT name, but any symbol.
Some sort of namespace structuring might greatly relieve the burden on &SYSECT. Think of reviving the renaming rules for ALGOL 60's moribund call-by-name convention. How should XREF reflect the use of qualified multiple names? -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
