Here there be dragons. Comments that explain what is already clear can clutter
the code and make it harder to read. By all means document adequately, but
don't simply echo the semantics of the code for the purported benefit of
newbies. Even newbies can be distracted by unnecessary comments.
ObSyntaxRant There are languages where it is always possible to add a comment
at the end of a statement; why does HLASM require a delimiter that is not
always permissible? If it's the only way to add a comment, why should one of
these be valid and the other not
label FOO , comment
label BAR , comment
where FOO has optional positional parameters and BAR has no positional
parameters.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Paul Gilmartin [00000014e0e4a59b-dmarc-requ...@listserv.uga.edu]
Sent: Friday, May 27, 2022 11:31 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Generating a TR field
On May 26, 2022, at 16:26:38, Charles Mills wrote:
>
> And what is that? Some comments?
>
My thought, but what?:
A paraphrase of the OP's requirement?
And/or explanation of the unintuitive semantics of:
o "*" within a repetitive constant definition?
o A character self-defining term used as a numeric value?
o "ORG" with *two* empty arguments?
But no fault to Ed. His target was a level above your
putative "maintenance newbie" and valued brevity.
>> @Ed's approach is elegant, although a maintenance newbie might have
> trouble understanding what 256AL1(*-TABLE) did.
>>
> Troublesome only because Ed left out the most important thing.
>
>> -----Original Message-----
>> From: Ed Jaffe
>> Sent: Thursday, May 26, 2022 2:36 PM
>>
>> What you want should be trivial:
>> |TABLE DC 256AL1(*-TABLE)
>> | ORG TABLE+C'*'
>> | DC CL1' '
>> | ORG ,
>
> --
> gil
--
gil
Моё судно на воздушной подушке полно угрей.
