Article View: bit.listserv.asm370
Article #53Re: Named PUSH/PUP suggestion
From: David Cole
Date: Mon, 03 Oct 2005 19:00
Date: Mon, 03 Oct 2005 19:00
40 lines
3647 bytes
3647 bytes
<html> <body> Hi John,<br><br> No, I wasn't thinking of "any order".<br><br> A named POP would pop both the named environment as well as all newer environments (possibly with an optional warning message?).<br><br> So environments would still be POP'd in the order of newest to oldest.<br><br> But that's not my primary interest. My primary interest would be for the Assembler to simply allow names on the PUSH/POP statements, even if it did nothing with those names at all. Just <u>having</u> matching names makes it easier to find unmatched PUSH's or POP's.<br><br> (Also, the name space for PUSH/POPs should be its own. I can think of no reason why it would cause a problem for a name on a PUSH/POP to be the same as a name on a normal statement. In fact, allowing such would actually be a benefit. In my own code, I often bracket my subroutines with "PUSH/POP USING" statements, and I find it to be a convenience to give the same name to the PUSH/POPs as I do to the subroutine.)<br><br> Thanks,<br> Dave<br><br> <br> At 10/3/2005 02:27 PM, John R. Ehrman wrote:<br> <blockquote type=cite class=cite cite="">If I read your suggestion correctly, it seems like you want to<br> "SAVE" and "RESTORE" an environment rather to PUSH or POP it.<br><br> That is, RESTOREs are not done in reverse order of SAVEs, but<br> any any order you like?<br> John Ehrman<br> (------------------ Referenced Note Follows --------------------)<br> Date: Sun, 2 Oct 2005 10:13:24 -0400<br> From: David Cole <dbcole@colesoft.com><br> ...<br> Recently it occurred to me, why don't I give my PUSH and POP<br> statements matching names...<br> ...</blockquote></body> </html>
Technical Details
Message-ID:
<6.2.3.4.2.20051003144958.03b86668@mail.swcp.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news.glorb.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-03!sn-xit-10!sn-xit-01!sn-xit-08!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!colesoft.com!dbcoleReferences:
<200510031827.j93IRoDD012393@d03av01.boulder.ibm.com>Show Full Headers
Complete Article Headers
X-Google-Thread: fcdcb,f622ba550323cb9
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news.glorb.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-03!sn-xit-10!sn-xit-01!sn-xit-08!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: Re: Named PUSH/PUP suggestion
Date: Mon, 3 Oct 2005 15:00:00 -0400
Organization: SAS Inc.
Lines: 40
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <6.2.3.4.2.20051003144958.03b86668@mail.swcp.com>
References: <200510031827.j93IRoDD012393@d03av01.boulder.ibm.com>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1128366323 11552 10.19.150.41 (3 Oct 2005 19:05:23 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Mon, 3 Oct 2005 19:05:23 +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=-0.1 required=10.0 tests=ALL_TRUSTED,HTML_10_20,
HTML_MESSAGE,MIME_HTML_ONLY autolearn=failed version=3.0.4
Approved-By: David Cole <dbcole@COLESOFT.COM>
In-Reply-To: <200510031827.j93IRoDD012393@d03av01.boulder.ibm.com>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 03 Oct 2005 19:05:22.0117 (UTC)
FILETIME=[674E9F50:01C5C84D]
Originator: daemon@mozart.unx.sas.com