Article View: bit.listserv.asm370
Article #306Re: Assembly coding guidelines
From: Robert A. Rosenberg
Date: Mon, 05 Sep 2005 03:02
Date: Mon, 05 Sep 2005 03:02
38 lines
3468 bytes
3468 bytes
At 14:25 -0400 on 09/04/2005, Paul Hanrahan wrote about Re: Assembly coding guidelines: >Continuing to the next line is useful but not something that should be done >often. 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)? > >-----Original Message----- >From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] >On Behalf Of Robert A. Rosenberg >Sent: Saturday, September 03, 2005 11:00 PM >To: ASSEMBLER-LIST@LISTSERV.UGA.EDU >Subject: Re: Assembly coding guidelines > > >At 09:39 -0400 on 09/03/2005, Paul Hanrahan wrote about Re: Assembly coding >guidelines: > >>What I found the most annoying about coding assembler was the comments. >>The area for a sequence number and then a code to identify the >>programmer digs into available space for comments. Using the comment >>line for change management identification tied back to a change log at >>the top of the program in a flower box is a good thing but then with >>extended opcodes the space on a line is reduced. >> >>I like having a programmer id on each line of code for root cause >>analysis but hate giving up space for line comments. > >Throw an "*" in column 72 and you have the next line for more comment text. >As an alternative, I often throw an "*" into column 1 and continue my >comment on that line in column 36 (My Start of Comment location).
Technical Details
Message-ID:
<p06230900bf416442e778@[192.168.1.11]>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!news.tele.dk!news.tele.dk!small.news.tele.dk!sn-xit-03!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!rarpsl.com!asmReferences:
<002b01c5b17d$f5fa5820$8401a8c0@DGG2YZ51>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!news2.google.com!proxad.net!news.tele.dk!news.tele.dk!small.news.tele.dk!sn-xit-03!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!rarpsl.com!asm
From: "Robert A. Rosenberg" <asm@rarpsl.com>
Newsgroups: bit.listserv.asm370
Subject: Re: Assembly coding guidelines
Date: Sun, 4 Sep 2005 23:02:04 -0400
Organization: SAS Inc.
Lines: 38
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <p06230900bf416442e778@[192.168.1.11]>
References: <002b01c5b17d$f5fa5820$8401a8c0@DGG2YZ51>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1125894530 10896 10.19.150.41 (5 Sep 2005 04:28:50 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Mon, 5 Sep 2005 04:28:50 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
X-Mailer: Eudora for Mac OS X 6.2.3 (MacOS 10.3)
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - server70.totalchoicehosting.com
X-AntiAbuse: Original Domain - listserv.uga.edu
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - rarpsl.com
Approved-By: "Robert A. Rosenberg" <asm@RARPSL.COM>
In-Reply-To: <002b01c5b17d$f5fa5820$8401a8c0@DGG2YZ51>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 05 Sep 2005 04:28:47.0879 (UTC)
FILETIME=[4F21C970:01C5B1D2]
Originator: daemon@mozart.unx.sas.com