Named PUSH/PUP suggestion

Article View: bit.listserv.asm370

Article #44

Back to bit.listserv.asm370 Previous Next

#44

From: David Cole
Date: Sun, 02 Oct 2005 14:13

25 lines
2898 bytes

Sometimes when developing code I mismatch my Assembler PUSH/POP
statements, and finding the excess PUSH or POP often is a tedious process.

As it happens (and for unrelated reasons), I often replace the
Assembler PUSH/POP instructions with macros.

Recently it occurred to me, why don't I give my PUSH and POP
statements matching names... Well, the native PUSH/POP statements do
not permit name fields, but since I'm using my own macros, then why not...

Two advantages arise. First, with matching name fields, it's now very
easy for me to find unmatched PUSH/POPs.

Second, the name could serve as tokens allowing for a single POP to
pop all PUSH's at and lower than the corresponding named PUSH.

Third, if a named POP does not have a corresponding PUSH, then the
assembler could flag that error on the spot.

What do you think?

Dave Cole              REPLY TO: dbcole@colesoft.com
Cole Software          WEB PAGE: http://www.xdc.com
736 Fox Hollow Road    VOICE:    540-456-8536
Afton, VA 22920        FAX:      540-456-6658

Technical Details

Message-ID: <6.2.3.4.2.20051002100259.03be4008@mail.swcp.com>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!newsread.com!news-xfer.newsread.com!newspeer.tds.net!sn-xit-02!sn-xit-06!sn-xit-05!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!colesoft.com!dbcole

References: <6F4F88E09079204787D7CD2FB91FA8FE01793CAD@hqmail.rocketsoftware.com>

Show Full Headers

Complete Article Headers

X-Google-Thread: fcdcb,f622ba550323cb9,start
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!newsread.com!news-xfer.newsread.com!newspeer.tds.net!sn-xit-02!sn-xit-06!sn-xit-05!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!colesoft.com!dbcole
From: David Cole <dbcole@colesoft.com>
Newsgroups: bit.listserv.asm370
Subject: Named PUSH/PUP suggestion
Date: Sun, 2 Oct 2005 10:13:24 -0400
Organization: SAS Inc.
Lines: 25
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <6.2.3.4.2.20051002100259.03be4008@mail.swcp.com>
References: <6F4F88E09079204787D7CD2FB91FA8FE01793CAD@hqmail.rocketsoftware.com>
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 1128262928 31458 10.19.150.41 (2 Oct 2005 14:22:08 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Sun, 2 Oct 2005 14:22:08 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
X-Virus-Scanned: ClamAV 0.87/1107/Sun Oct  2 02:09:39 2005 on av1
X-Virus-Status: Clean
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on kaimen.swcp.com
X-Spam-Status: No,
               hits=-2.4 required=10.0 tests=ALL_TRUSTED autolearn=failed
               version=3.0.4
Approved-By: David Cole <dbcole@COLESOFT.COM>
In-Reply-To: <6F4F88E09079204787D7CD2FB91FA8FE01793CAD@hqmail.rocketsoft
              ware.com>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 02 Oct 2005 14:22:05.0601 (UTC)
                       FILETIME=[AA2E5910:01C5C75C]
Originator: daemon@mozart.unx.sas.com

Reply to Parent Message