should this application has been mine, I would define the DSECT's with some
macro that could add a prefix or suffix to the name (assembler does support
long names nowadays) and the reference would be done with some conditional
assembly that would be sensitive to the prefix/suffix as well.
Assembler never had compile time namespaces (the idea of name spaces came about
much after Assembler has been invented), so the way to deal with that was
always via the venerable &sysndx and/or some clever GBLC programming
Ze'ev Atlas
From: John Ehrman <[email protected]>
To: [email protected]
Sent: Thursday, April 14, 2016 3:52 PM
Subject: Re: ASM0A43E Previously Defined Symbol
Two comments:
(1) Mike La Martina wrote
>One would think so but HLASM does not have scoped namespaces.
>My suggestions for such have been summarily dismissed.
Your suggestion wasn't "summarily dismissed" -- it's just that it would
require substantial internal modifications to the assembler. We don't
(and didn't) have sufficient resources to do it. Perhaps we didn't reply
tactfullly.
(2) Michael Butz asked
>If I have to two dsects with the same label and I qaulify the usage of
the dsect with a label on the using shouldn't that do away with above
error message
In your example, the DSects had different names, but each contained a
field with the same name. Currently, HLASM can support only a single
instance of an internal symbol, so using the same symbol in two different
DSects won't work. Sorry!
Regards... John
