13 The optional Locals word set
13.1 Introduction
13.2 Additional terms and notation
None.
13.3 Additional usage requirements
13.3.1 Locals
A local is a data object whose execution semantics shall return its
value, whose scope shall be limited to the definition in which it is
declared, and whose use in a definition shall not preclude reentrancy
or recursion.
13.3.2 Environmental queries
Append table
13.1 to table
3.4.
See:
3.2.6 Environmental queries.
Table 13.1: Environmental Query Strings
|
String Value data type | Constant? | Meaning |
|
#LOCALS | n | yes
| maximum number of local variables in a definition |
|
|
13.3.3 Processing locals
To support the locals word set, a system shall provide a mechanism
to receive the messages defined by
(LOCAL) and respond as
described here.
During the compilation of a definition after
: (colon),
:NONAME, or
DOES>, a program may begin
sending local identifier messages to the system. The process shall
begin when the first message is sent. The process shall end when the
"last local" message is sent. The system shall keep track of the
names, order, and number of identifiers contained in the complete
sequence.
13.3.3.1 Compilation semantics
The system, upon receipt of a sequence of local-identifier messages,
shall take the following actions at compile time:
- Create temporary dictionary entries for each of the
identifiers passed to (LOCAL), such that each identifier
will behave as a local. These temporary dictionary
entries shall vanish at the end of the definition, denoted by
; (semicolon), ;CODE, or
DOES>. The system need not maintain these
identifiers in the same way it does other dictionary entries
as long as they can be found by normal dictionary searching
processes. Furthermore, if the Search-Order word set is present,
local identifiers shall always be searched before any of the
word lists in any definable search order, and none of the
Search-Order words shall change the locals' privileged position
in the search order. Local identifiers may reside in mass storage.
- For each identifier passed to (LOCAL), the system shall
generate an appropriate code sequence that does the following at
execution time:
- Allocate a storage resource adequate to contain the value
of a local. The storage shall be allocated in a way that
does not preclude re-entrancy or recursion in the definition
using the local.
- Initialize the value using the top item on the data stack.
If more than one local is declared, the top item on the
stack shall be moved into the first local identified, the
next item shall be moved into the second, and so on.
The storage resource may be the return stack or may be
implemented in other ways, such as in registers. The storage
resource shall not be the data stack. Use of locals shall not
restrict use of the data stack before or after the point of
declaration.
- Arrange that any of the legitimate methods of terminating
execution of a definition, specifically ;
(semicolon), ;CODE, DOES> or
EXIT, will release the storage resource allocated
for the locals, if any, declared in that definition.
ABORT shall release all local storage resources,
and CATCH / THROW (if
implemented) shall release such resources for all definitions
whose execution is being terminated.
- Separate sets of locals may be declared in defining words
before DOES> for use by the defining word, and
after DOES> for use by the word defined.
A system implementing the Locals word set shall support the
declaration of at least sixteen locals in a definition.
13.3.3.2 Syntax restrictions
Immediate words in a program may use
(LOCAL) to implement
syntaxes for local declarations with the following restrictions:
- A program shall not compile any executable code into the
current definition between the time (LOCAL) is executed
to identify the first local for that definition and the time of
sending the single required "last local" message;
- The position in program source at which the sequence of
(LOCAL) messages is sent, referred to here as the point
at which locals are declared, shall not lie within the scope of
any control structure;
- Locals shall not be declared until values previously placed on
the return stack within the definition have been removed;
- After a definition's locals have been declared, a program may
place data on the return stack. However, if this is done,
locals shall not be accessed until those values have been
removed from the return stack;
- Words that return execution tokens, such as '
(tick), ['], or FIND, shall not be
used with local names;
- A program that declares more than sixteen locals in a single
definition has an environmental dependency;
- Locals may be accessed or updated within control structures,
including do-loops;
- Local names shall not be referenced by POSTPONE
and [COMPILE].
See:
3.4 The Forth text interpreter.
13.4 Additional documentation requirements
13.4.1 System documentation
13.4.1.1 Implementation-defined options
13.4.1.2 Ambiguous conditions
- executing a named local while in interpretation state
(13.6.1.0086 (LOCAL));
- a local name ends in "
:
", "[
", "^
";
- a local name is a single non-alphabetic character;
- the text between {: and
:}
extends over more than one line;
- {: ...
:}
is used more than once in a word.
13.4.1.3 Other system documentation
- no additional requirements.
13.4.2 Program documentation
13.4.2.1 Environmental dependencies
13.4.2.2 Other program documentation
- no additional requirements.
13.5 Compliance and labeling
13.5.1 Forth-2012 systems
The phrase "Providing the Locals word set" shall be appended to
the label of any Standard System that provides all of the Locals
word set.
The phrase "Providing
name(s) from the Locals Extensions
word set" shall be appended to the label of any Standard System
that provides portions of the Locals Extensions word set.
The phrase "Providing the Locals Extensions word set" shall be
appended to the label of any Standard System that provides all of
the Locals and Locals Extensions word sets.
13.5.2 Forth-2012 programs
The phrase "Requiring the Locals word set" shall be appended to
the label of Standard Programs that require the system to provide
the Locals word set.
The phrase "Requiring
name(s) from the Locals Extensions
word set" shall be appended to the label of Standard Programs that
require the system to provide portions of the Locals Extensions word
set.
The phrase "Requiring the Locals Extensions word set" shall be
appended to the label of Standard Programs that require the system
to provide all of the Locals and Locals Extensions word sets.
13.6 Glossary
13.6.1 Locals words
13.6.2 Locals extension words