Article View: bit.listserv.asm370
Article #305Re: Assembly coding guidelines
From: McKown, John
Date: Mon, 05 Sep 2005 02:17
Date: Mon, 05 Sep 2005 02:17
45 lines
3487 bytes
3487 bytes
> -----Original Message----- > From: IBM Mainframe Assembler List > [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Bill Fairchild > Sent: Saturday, September 03, 2005 8:57 AM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: Assembly coding guidelines > > > In a message dated 9/3/2005 8:40:24 A.M. Central Daylight > Time, p_hanrahan@sbcglobal.net writes: > > >The area for a sequence number and then a code to identify the > >programmer > digs > >into available space for comments. ... but then with extended > >opcodes the space on a line is reduced. > > > > Which is another reason why I still confine my statement > labels to eight characters, just as I was forced to do for my > first several decades of Assembler coding by the primitive > Assemblers of those ancient times, even though now more > modern Assemblers will let me add underscores and extend the > names almost as far as the eye can see. > > Bill Fairchild > To me, the next step in HLASM intelligent design would be to abandon the archaic 80 column card format entirely. Why is it there any more? Or course, a 200 character line would likely be enough to infuriate any good HLASM programmer. But a nice 100 character line could be useful. John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited.
Technical Details
Message-ID:
<80ED1590A931EE45BAE1DA52D25AE0F2E0B84E@UICNRHECHP6.uicnrh.dom>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!uiciinsctr.com!john.mckownShow 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!uiciinsctr.com!john.mckown
From: "McKown, John" <john.mckown@uiciinsctr.com>
Newsgroups: bit.listserv.asm370
Subject: Re: Assembly coding guidelines
Date: Sun, 4 Sep 2005 21:17:29 -0500
Organization: SAS Inc.
Lines: 45
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <80ED1590A931EE45BAE1DA52D25AE0F2E0B84E@UICNRHECHP6.uicnrh.dom>
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 1125887137 6894 10.19.150.41 (5 Sep 2005 02:25:37 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Mon, 5 Sep 2005 02:25:37 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: Assembly coding guidelines
Thread-Index: AcWwkAf48N+gxUJvS16eBys06dLWbgBL4tWQ
X-OriginalArrivalTime: 05 Sep 2005 02:17:29.0953 (UTC)
FILETIME=[F785AD10:01C5B1BF]
X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.cc.uga.edu id
j852HULR007480
Approved-By: "McKown, John" <john.mckown@UICIINSCTR.COM>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-Mime-Autoconverted: from 8bit to 7bit by mime827
Originator: daemon@mozart.unx.sas.com