Robert,
I would describe what is happening more precisely. When you hit your
, you are NEVER calling "a frame" or your true target frame; instead
you are ALWAYS calling U2 frame PRSCMLINE, only. PRSCMLINE, in its turn ...
I never thought of that; thanks for pointing it out.
Re: Mr. regnawsniB (how does he pronounce yrraH?):
"yah-RAW."
> Does it have to be [in a subroutine] , or would this be as good:
>JM 2.childframeQ2
It doesn't HAVE to be, but you should understand the difference, which is
night
and day. If you do >, then you put the current content of S/G 00,
whatever it is, in S/G 50. The current content of S/G 00 may not be what you
think it is, or what you started out with; and it may have nothing to do with
the command line.
Right.
The SUbroutine does something COMPLETELY different, and
really unrelated: It reads the *current* CMline in its entirety, from
start to
finish. Current, mind you! Whatever is there NOW is what gets read, so you
gotta know what's there -- have you disturbed the CMline since you started?
altered it? wiped it? That is entirely unrelated to, say, the value of 00
when you RUN a standalone program, where 00 simply holds any arguments,
but NOT
the RUN command or programname! With the SUb, you get the whole line.
Aha. That's a little different from what it was in Xy3 isn't it? I seem to
recall that in Xy3, 00 would include the RUN and program name.
Harry Binswanger
hb@xxxxxxxx