Opinion on best practice...

Chris Angelico rosuav at gmail.com
Fri Feb 8 19:28:06 EST 2013


On Sat, Feb 9, 2013 at 5:29 AM, Dennis Lee Bieber <wlfraed at ix.netcom.com> wrote:
>         If you want the real nightmare -- look into the IBM "queue" scheme
> (not many REXX implementations except on IBM mainframes support that).
> One can push lines onto the queue, such that when the script exits, the
> command  processor reads those lines first before reading from
> keyboard... Or push lots of text in a way that the next script to start
> reads it without using a temporary file. IBM mainframes didn't
> "multitask" too well <G>; no easy creation of processes with pipes
> between them.

Heh. The OS/2 implementation of REXX has that too, but also has much
easier piping mechanisms... and, ironically, provides a convenient way
to pipe text into your script using the RXQUEUE external command:

"some_command | rxqueue /fifo"
do while queued()>0
    parse pull blah blah blah
end

ChrisA



More information about the Python-list mailing list