|
<< Click to Display Table of Contents >> Navigation: 3. Script Language > Stack-Operations > Stack Commands |
MiniRobotLanguage (MRL)
PUS. Command
Push parameter onto User Stack
Intention
Pushes the complete parameter on top of the User-Stack.
Variables or special-folders are not processed.
You can PUV. any Stack Content into the variable(s).
While PVS. and PUS. explicitly does NOT resolve variables and special-folder, POP. PUV. PSS., PNS do just that.
To avoid Variable Resolution when taking things from the Stack, you can use POV. or
VAO.$$VAR=$$000
PVS. - Put Variable-Name on Stack without resolving anything
PSS. - Resolve Variables and Special-Folders before putting the Variable on Stack
PNS. - Do a numerical resolution and calculate Formulas in the Variable (if they are in ()). Then put the result on TOS.
PUV. - Do a Variable-Type dependent Variable resolution. Variables that are defined in some way have a Variable-Type (See GVT.-Command)
PUS. - Put Variable-Name on Stack without resolving anything. Unlike PVS., Variables will not be split if separated with |"|". Just the whole Parameter will be placed on TOS.
Syntax
PUS.[P1]
Parameter Explanation
P1 - String
The Stack being used is the actual User-Stack.
It can be the Local User Stack or the Global User-Stack, which depends on settings done with STS.-Command.
If the popped items are deleted from stack or not also depends on the settings done with STS.
Speed in Ticks:
This command uses typically around 23 Ticks.
Example
DBM.2
PRT.Items on Stack: #tos#
: $$TXA=Laba
: $$TXB=Lax
PRT. Variables Content (1): $$TXA-$$TXB
PUS.$$TXA|$$TXB
PRT. Items on Stack: #tos#
PRT. Item on TOS: <$dtos$>
DMP.4
END.
Remarks
-
Limitations:
-
See also:
• STV. - Stack To/from Variable
• PUS. - Push Parameter onto Stack/Que
• POP. - POP Variable from Stack
• POV. - POp Variables from User-Stack