RpnStack: Difference between revisions
Jump to navigation
Jump to search
Gordon.dye (talk | contribs) (→Syntax) |
Gordon.dye (talk | contribs) |
||
Line 11: | Line 11: | ||
====Technical Considerations==== | ====Technical Considerations==== | ||
# RpnStack may be specified only in the [[BRConfig.sys]] file; it is '''not''' valid with [[Config]]. | |||
# An error message (error code [[9002]]) appears when an RPN stack is too small for the program in use. | |||
# The amount of RPN stack memory available depends on the depth of function calls and complexity of expressions. Normally the RPN stack is cleared at the completion of each statement. However, stacked entries are suspended on the RPN stack when a function call is made. | |||
#The '''Status Stacks''' command shows the current stack settings. | |||
<noinclude> | <noinclude> | ||
[[Category:Config]] | [[Category:Config]] | ||
</noinclude> | </noinclude> |
Latest revision as of 00:00, 29 June 2015
The RpnStack config specification changes the size of the RPN stack, which holds the locations of each active variable in the current statement and the locations of statements suspended by a user-defined function call.
Syntax
- Start-up Default
RpnStack 1000 (version 4.3+)
Parameter
"Integer" is a decimal number representing the number of variables that the RPN stack can hold. It must be greater than 49; the default is 200 variables.
Technical Considerations
- RpnStack may be specified only in the BRConfig.sys file; it is not valid with Config.
- An error message (error code 9002) appears when an RPN stack is too small for the program in use.
- The amount of RPN stack memory available depends on the depth of function calls and complexity of expressions. Normally the RPN stack is cleared at the completion of each statement. However, stacked entries are suspended on the RPN stack when a function call is made.
- The Status Stacks command shows the current stack settings.