Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!elroy.jpl.nasa.gov!decwrl!nsc!amdahl!terry
From: terry@uts.amdahl.com (Lewis T. Flynn)
Newsgroups: comp.lang.rexx
Subject: Re: Using the system stack
Message-ID: <0cza01Jn051k00@amdahl.uts.amdahl.com>
Date: 10 Jan 91 17:55:20 GMT
References: <1991Jan09.180541.4246@eecs.wsu.edu>
Reply-To: terry@amdahl.uts.amdahl.com (Lewis T. Flynn)
Organization: Amdahl Corporation, Sunnyvale CA
Lines: 14

In article <1991Jan09.180541.4246@eecs.wsu.edu> dfrank@yoda.UUCP (Duane D. Frank) writes:
>My question is:  If I want to call this GREP exec from another exec or
>function, and I want the GREP program to put it's output information on
>the system stack so it can be pulled off by the calling EXEC, (with a 
>do while queued() for instance) how would I go about putting the output
>information onto the stack?

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
and thus doesn't disturb any thing which is already there. If you can
guarantee that the stack is empty, then using the 'queue' command will
stack it fifo. Type 'help rexx push' or 'help rexx queue' for more info.

Terry