>> I don't see a description of the continuation rules for a SYSIN containing a mixture of flowed and unflowed records.
I have source members that have a mixture of flowasm style and traditional continued source and there is not a problem. In the past I have used the traditional continuation format for things like long character literals so that ISPF highlighting is not confused and the constants are easier on the eye. In the same member, normal executable code would be in flowasm format and I just lived with the ISPF highlighting failures (not a problem for me now with SlickEdit). 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. (o) Sanity is preserved by not mixing flowasm+traditional lines in the same logical statement. Is it possible for FLOWASM to get confused by innocent code that has a “non-space followed by comma” as the last data on the line? Yes Are there IBM/ISV macros that cause the above to happen? Yes – and there is an exclusion table in the exit source to disable flowasm processing for named macros. Is flowasm perfect? No – but what it offers is immense (IMHO) compared to any minor inconveniences. I would love IBM HLASM to embrace what Ed has done here and include this feature as on option in ASMA90. Rob From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: 07 June 2021 17:31 To: [email protected] Subject: Re: Slickedit now supports FLOWASM syntax highlighting for HLASM EXTERNAL EMAIL On Mon, 7 Jun 2021 07:29:37 +0000, Rob Scott wrote: >For the record, Ed's presentation can be found at the following link : > Thanks. >https://phoenixsoftware.com/ftp/demo/Structured_Assembler.pdf<https://phoenixsoftware.com/ftp/demo/Structured_Assembler.pdf> > Where I read: • FLOWASM is written using SPMs but does not depend on itself for obvious reasons. That's not obvious. Many language processors, even HLASM, are written in and depend on the languages they support, after bootstrapping. • For z/OS, supports both fixed and variable length source (SYSIN) input. ... • Library(SYSLIB) input still restricted to LRECL=80. • We use only RECFM=FB LRECL=80 source libraries. Ouch! I suppose that's imposed by the SYS1.MACLIB catenand. I don't see a description of the continuation rules for a SYSIN containing a mixture of flowed and unflowed records. Thanks again, gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[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
