Re: Assembly coding guidelines

Article View: bit.listserv.asm370

Article #332

Back to bit.listserv.asm370 Previous Next

#332

From: Paul Hanrahan
Date: Tue, 06 Sep 2005 12:45

35 lines
3314 bytes

I'm not sure what you mean by a tabular form. True fonts with column
orientation and prefix numbers and column numbers as opposed to proportional
fonts without the editor providing visible line and column numbers are
comfort items that a more GUI development environment for assembler could
maintain.

I think the death nell is being rung for SCLM and ISPF so why not spruce up
assembler a little by perhaps making 100 columns the norm and moving the
continuation column ?

-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Gerhard Postpischil
Sent: Monday, September 05, 2005 9:20 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Assembly coding guidelines

Robert A. Rosenberg wrote:
> I was just pointing out that continuing the comment on the next card
> is a "solution" to the stated "problem" of the lack of space on the
> line due to other required data. If your comment needs to be
> x-characters long, what is the difference between it taking up one or
> two lines (the latter due to there not being enough room on the first
> line)?

The assembler is faster to work with due to the tabular form of its input
(and output). While continuations are sometimes unavoidable, they break the
visual flow. Voluminous comments look better in a "flower box" preceding a
group of lines, than as continued comments. At best, the continuation
comment should start after column 20 so as not to interfere with the
instruction column.

Gerhard Postpischil
Bradford, VT

Technical Details

Message-ID: <000001c5b2e0$e471aa40$8701a8c0@DGG2YZ51>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-03!sn-xit-11!sn-xit-05!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!sbcglobal.net!p_hanrahan

Show Full Headers

Complete Article Headers

X-Google-Thread: fcdcb,b5f541d74f4633a6
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-03!sn-xit-11!sn-xit-05!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!sbcglobal.net!p_hanrahan
From: Paul Hanrahan <p_hanrahan@sbcglobal.net>
Newsgroups: bit.listserv.asm370
Subject: Re: Assembly coding guidelines
Date: Tue, 6 Sep 2005 08:45:41 -0400
Organization: SAS Inc.
Lines: 35
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <000001c5b2e0$e471aa40$8701a8c0@DGG2YZ51>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1126011045 27360 10.19.150.41 (6 Sep 2005 12:50:45 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Tue, 6 Sep 2005 12:50:45 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.cc.uga.edu id
                      j86CjhAj012253
Approved-By: Paul Hanrahan <p_hanrahan@SBCGLOBAL.NET>
In-Reply-To: <431C4605.5050101@valley.net>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 06 Sep 2005 12:50:43.0296 (UTC)
                       FILETIME=[97BB7E00:01C5B2E1]
X-Mime-Autoconverted: from 8bit to 7bit by mime827
Originator: daemon@mozart.unx.sas.com