This sounds like a C person trying to get Assembler to conform to C coding expectations. Is that a correct perception? -------------------------------------------- On Tue, 2/28/17, ASSEMBLER-LIST automatic digest system <[email protected]> wrote:
Subject: ASSEMBLER-LIST Digest - 27 Feb 2017 to 28 Feb 2017 (#2017-17) To: [email protected] Date: Tuesday, February 28, 2017, 11:00 PM ASSEMBLER-LIST Digest - 27 Feb 2017 to 28 Feb 2017 (#2017-17) #yiv1587356787 body { font-family:Arial, Helvetica, sans-serif;font-size:12px;color:#000000;} #yiv1587356787 td { font-family:Arial, Helvetica, sans-serif;font-size:12px;color:#000000;} #yiv1587356787 p { font-family:Arial, Helvetica, sans-serif;font-size:12px;color:#000000;} #yiv1587356787 a { font-family:Arial, Helvetica, sans-serif;font-size:12px;font-weight:bold;color:#3366CC;text-decoration:none;} #yiv1587356787 h2 { font-family:Arial, Helvetica, sans-serif;font-size:17px;font-weight:bold;color:#CC0033;} #yiv1587356787 h3 { font-family:Arial, Helvetica, sans-serif;font-size:16px;font-weight:bold;color:#3366CC;} ASSEMBLER-LIST Digest - 27 Feb 2017 to 28 Feb 2017 (#2017-17) Table of contents: HLASM anomaly (2) HLASM anomaly HLASM anomaly (02/28) From: Melvyn Maltz <[email protected]> Re: HLASM anomaly (02/28) From: Paul Gilmartin <[email protected]> Browse the ASSEMBLER-LIST online archives.
