Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!zaphod.mps.ohio-state.edu!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga
Subject: Re: Help with EXPOSE in ARexx requested
Message-ID: <1131@lpami.wimsey.bc.ca>
Date: 10 Feb 90 14:57:03 GMT
Lines: 35
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <385@icebox.nsc.com>, waggoner@dtg.nsc.com (Mark Waggoner) writes:
>In article <10665@nigel.udel.EDU> new@udel.edu (Darren New) writes:
>>
>>Any help here, no matter how kludgey, would be appriciated.  How do I
>>get to the caller's variables from a separate-file ARexx macro called from
>>ARexx?                     -- Darren
>
>I don't believe you can expose variables that were initailized in a
>separate-file ARexx macro.  The ways that I can think of doing it
>would be to put the values you want to modify on the clip list or 
>to return a string from your procedure that contains rexx instructions
>to set the variable values.  The caller can then interpret the
>returned string to set the variable values.

Right. A few other ways...

Have the called macro send output to stdout, and when you call it, pipe the
output to execio (comes with WShell).

Have the called macro use QUEUE or PUSH to stack the variables, then read them
in the calling macro with PULL or with a file operation (READLN(), READCH() ),
using stdin as a file spec.

Have the called program send a message to the caller via PutMsg().

-larry

--
Gallium Arsenide is the technology of the future;
  always has been, always will be.
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+