>>(a) imposes a severe restriction on the long-lines facility by requiring that 
>>column 72 be blank.  The programmer could accommodate that by coding such as 
>>0C' ', but that's worse than old-fashioned continuation.

I re-read the commentary in the exit this morning and it states :

"Source input may be any of the following :

1) Fixed records of any size. Sequence numbers are allowed in columns LRECL-7 
through LRECL.
The  continuation column is LRECL-8.

2) Variable length records without sequence numbers.  Continuation is indicated 
with a trailing '+' character.

3) Variable length records with sequence numbers in columns 1-8. Continuation 
is indicated with a trailing '+' character.

...."

I think (1) solves the restriction you mentioned and is actually better than I 
guessed yesterday.

As regards the "scrunching", here is the comments from the code :

"Blank Elimination / Wrapping of Long Lines:

If a statement is too long to fit in a standard 80-byte assembler source line, 
the statement is reformatted as follows:

1) All extraneous blanks between the operation code and operand are eliminated.
2) If the statement is still too long, extraneous blanks between the operand 
and commentary are removed.
3) If the statement is still too long, extraneous blanks in front of the 
operation code are removed.
4) If the statement is still too long:
     a) If the operand fits on the line, the commentary is truncated.
     b) If the operand is too long to fit, it is wrapped  and continued in 
column 16 of the next line along with any commentary.  "

Rob Scott
Rocket Software


-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Paul Gilmartin
Sent: 07 June 2021 22:39
To: [email protected]
Subject: Re: Slickedit now supports FLOWASM syntax highlighting for HLASM

EXTERNAL EMAIL





On Mon, 7 Jun 2021 14:10:08 -0700, Charles Mills wrote:

>> What if both (a) and (b) are true?
>
>"Doc, when I hit my head with this hammer it hurts!"
>"Don't do that."
>
(a) imposes a severe restriction on the long-lines facility by requiring that 
column 72 be blank.  The programmer could accommodate that by coding such as 
0C' ', but that's worse than old-fashioned continuation.

The documentation should state the rules completely and unambiguously.

FLOWASM's syntax is relatively good only insofar as HLASM's is absolutely bad.


>-----Original Message-----
>From: Paul Gilmartin
>Sent: Monday, June 7, 2021 12:20 PM
>On Mon, 7 Jun 2021 18:02:57 +0000, Rob Scott wrote:.
>>
>>As for the rules, this is what I use (Ed can correct me if I am wrong).
>>
>>(o) If the first line of a logical statement has a character in col-72, it 
>>will not be processed by flowasm and presented to ASMA90 as-is.
>>
>>(o) If the first line of a logical statement can be processed in flowasm 
>>format, it will be dynamically changed to traditional format before being 
>>presented to ASMA90. Subsequent lines in the same logical statement are 
>>required to be in flowasm format.
>>    ...

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to