akcs.scotty@hpcvbbs.UUCP (SCOTTY THOMPSON) (05/05/91)
Upon using DSN's Voyager, and looking at the examples for System RPL programming and M/L programming, I came across items like: Set last RPL token to <0h> and verify depth >= 1 I would like to be educated as to what the hell an RPL token is (a pointer?--for what?) and how they affect programs (please!). I noticed some of the internal routines that would pop tokens, execute the next token, etc., but I have no idea what a "token" is here. Please help. Thanks. Scotty (213) 539-3611 (Wk), (213) 539-9780 (Hm) Call, leave mail, or respond here. I'll try to return a favor.
akcs.wilsonpm@hpcvbbs.UUCP (Pete M. Wilson) (06/09/91)
In item 1745, Falco (Andrey Dolgachev) asks: > Second of all, in the Nickel's Internals List there is mention of tokens. > Exactly what are they. I guess that they are used like the Tokens in the > token-ring network for computers, to control instructions , but I'm not > sure. and Derek Nickel replys: > Falco, > > I picked up the term 'token' from Pete Wilson. Since it has at least two > possable meanings (for a '48), I am not really happy with it. > > 1) In statements like "save last RPL token": A token is the "COMMAND". > > 2) In statements like "skip next token" or "do next token": A token is > an object (Real Number, Program, Graphic, etc). > > I plan to rename these comments in Voyager V1.0-6 > > Derek S. Nickel Pete Wilson
akcs.scotty@hpcvbbs.UUCP (SCOTTY THOMPSON) (06/15/91)
After hacking for awhile, I was able to determine exactly what these
"Tokens" were. However, to reitterate a previous post, nested tokens
like:
D9D20 [PROGRAM]
..... {COMMANDS}
XXXXX SKIP NEXT TOKEN
D9D20 [PROGRAM]
..... {COMMANDS}
D9D20 [PROGRAM]
..... {COMMANDS}
XXXXX SKIP NEXT TOKEN
B2130 [END_MARKER]
..... {COMMANDS}
B2130 [END_MARKER]
B2130 [END_MARKER]
don't seem to work if I have a "skip next token" preceeding an
end-marker. I would really like to know how to properly nest this type
of "token" list. For example, a simple IF THEN ELSE structure will
execute the next token and skip the next or skip this token and execute
the next. I know there are routines already in ROM that do this, but
they require that "TRUE" or "FALSE" (for example) be on the stack. I
wrote m/l routines that call skip next, etc. for quick analysis and
execution. Test routines in system RPL as described above behave
improperly when nested. Any help is muchly appreciated (it's SAT a.m.,
grammer and spelling become inverted and intertwined).
Derek, I'm going to send you a check for a few bucks for Voyager since I
have been using it considerably. Just a suggestion: PLEASE ALLOW US TO
EXIT AT ANY TIME FROM THE "PRESS ENTER TO CONTINUE" LINE AND EXAMINE
CODE. BETTER STILL, CAN WE PRESS A KEY TO "PUSH" THIS LOCATION, STOP
THERE, EXAMINE CODE AND UPON ENCOUNTERING GOYES' (ETC.), PUSH THOSE
ADDRESSES AND EXAMINE THE ROUTINES AND POP THEM TO RETURN OR HAVE A MENU
LIST POP UP TO SELECT THE RETURN "POP" ADDRESS?