On Fri, Feb 28, 2014 at 9:53 AM, Mark Miesfeld <miesf...@gmail.com> wrote:
>
> No statement in the Rexx program invokes the shell. It is this line:
>
> $rexx ~/rx/odd ?
>
> typed on the command line that <invokes> the shell. Although invokes is
> not really a good word. The shell has already been invoked and is sitting
> in a loop parsing stuff that is typed on the command line.
>
> The shell determines that odd is a file name and an executable file at
> that, uses the shebang line to determine the rexx executes the file. It
> then passes the file name and the command line arguments to rexx.
>
Well, that's not really correct, I didn't read that closely enough. The
shell determines the first token on the command line is an executable file,
rexx, and expands the rest of the command line into arguments it passes to
rexx.
--
Mark Miesfeld
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
