Article View: bit.listserv.asm370
Article #333Re: Assembly coding guidelines
From: McKown, John
Date: Tue, 06 Sep 2005 12:47
Date: Tue, 06 Sep 2005 12:47
41 lines
3570 bytes
3570 bytes
> -----Original Message----- > From: IBM Mainframe Assembler List > [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Craddock, Chris > Sent: Monday, September 05, 2005 11:53 AM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: Assembly coding guidelines > > > > 100 characters would work for me. Abandoning the sequence number and > > adding space would even be a good compromise at this point. While I > > love the ISPF sequence numbers at the start of a line the sequence > > numbers at the start of line have been optional for years in xedit. > > If you're one of those poor blighted souls who love ISPF, you might be > severely disappointed if you tried editing text files with record > lengths greater than the current screen width. ISPF is pretty > user-hateful on this. (Ask me how I know) > > Now admittedly you can define an emulator window with more than 80 > characters, so it's not entirely hopeless, but you'll be pretty > frustrated nevertheless. SPF/PC and its cousins are much superior in > this respect because they gracefully handle inserts, nulls etc. > > CC This is likely to be sacrilegious, but I really have gotten to like gvim on Linux. I don't know how to write "macros" for it, but I've not yet had too much of a need for that. I simply adore regular expressions. -- 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:
<80ED1590A931EE45BAE1DA52D25AE0F2E0B852@UICNRHECHP6.uicnrh.dom>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed.news2me.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-02!sn-xit-06!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!newsfeed.news2me.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-02!sn-xit-06!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: Tue, 6 Sep 2005 07:47:02 -0500
Organization: SAS Inc.
Lines: 41
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <80ED1590A931EE45BAE1DA52D25AE0F2E0B852@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 1126011142 27385 10.19.150.41 (6 Sep 2005 12:52:22 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Tue, 6 Sep 2005 12:52:22 +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: AcWyIUSZGXTHnOy/QPiwLn+RigHOEgAGK/PQACm4VOA=
X-OriginalArrivalTime: 06 Sep 2005 12:47:03.0259 (UTC)
FILETIME=[149482B0:01C5B2E1]
X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.cc.uga.edu id
j86Cl3V6012952
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