Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!elroy.jpl.nasa.gov!decwrl!mcnc!brooking
From: brooking@mcnc.org (Jim Brooking)
Newsgroups: comp.lang.rexx
Subject: Re: Using the system stack
Summary: more about the stack
Message-ID: <7529@alvin.mcnc.org>
Date: 10 Jan 91 21:09:53 GMT
References: <1991Jan09.180541.4246@eecs.wsu.edu> <0cza01Jn051k00@amdahl.uts.amdahl.com>
Organization: MCNC; RTP, NC
Lines: 24

In article <0cza01Jn051k00@amdahl.uts.amdahl.com>, terry@uts.amdahl.com (Lewis T. Flynn) writes:
> In article <1991Jan09.180541.4246@eecs.wsu.edu> dfrank@yoda.UUCP (Duane D. Frank) writes:
> > Deleted stuff
> 
> The usual way is to 'push' it (using the 'push' command) with some means
> of delimiting when you've reached the end. This puts it on the stack lifo
> etc.

You could find out if anything was on the stack before putting stuff
there thru the "queued()" function. The results of queued() could be
pushed onto the stack as the last thing there, so it could be read
by the receiving program which might look like:

	/* ob comment */

	pull count
	do until queued() = count /* or "do while queued > count" */
		pull line
	...


-- 
>8-}     >:-)     %\(     8^)     :+/     |'[     ;-)     :-O     B^\    :-)
Jim Brooking........North Carolina Supercomputing Center.......(919)248-1145