內容列表(Table of Contents)

A.2 專有名詞和標記法(Terms and notation)

模稜兩可的情況

一個標準系統對於一個模稜兩可的情況的回應將決定的能力留給實作者. 一個標準系統不需要明確地偵測或回報模稜兩可的情況的出現.

ambiguous condition

The response of a Standard System to an ambiguous condition is left to the discretion of the implementor. A Standard System need not explicitly detect or report the occurrence of ambiguous conditions.

交互編譯器

交互編譯器可以用來準備一個用來執行於內嵌式系統的程式, 或可以用來產生在相同或一個不相同的執行時期環境的 Forth 核心.

cross compiler

Cross-compilers may be used to prepare a program for execution in an embedded system, or may be used to generate Forth kernels either for the same or a different run-time environment.

資料欄位

在較早的標準中, 資料欄位是被認知為參數欄位.

在子程序序列 Forth 系統中, 每一件事物都是目的碼. 沒有傳統的程式碼或資料欄位. 只有一個由 CREATE 或是由呼叫 CREATE 的詞定義的詞有一個資料欄位. 只有一個由 CREATE 定義的資料欄位可以可移植性地操作.

data field

In earlier standards, data fields were known as parameter fields.

On subroutine threaded Forth systems, everything is object code. There are no traditional code or data fields. Only a word defined by CREATE or by a word that calls CREATE has a data field. Only a data field defined via CREATE can be manipulated portably.

詞集

這個標準看出有些函式, 雖然在某些應用領域很有用, 但是不足夠一般地證明在所有的 Forth 系統需要它們. 此外, 將 Forth 詞依照相關的函式分類成 Forth 詞將會是有幫助的. 這個議題用詞集的想法來處理.

核心 詞集包含了 Forth 系統必要的主體. 它是唯一必需的詞集. 其他定義於標準中的詞集是選用被附加的, 使得可以提供可修改性能等級的標準系統.

word set

This Standard recognizes that some functions, while useful in certain application areas, are not sufficiently general to justify requiring them in all Forth systems. Further, it is helpful to group Forth words according to related functions. These issues are dealt with using the concept of word sets.

The Core word set contains the essential body of words in a Forth system. It is the only required word set. Other word sets defined in this Standard are optional additions to make it possible to provide Standard Systems with tailored levels of functionality.

The use of -sys, orig, and dest data types in stack effect diagrams conveys two pieces of information. First, it warns the reader that many implementations use the data stack in unspecified ways for those purposes, so that items underneath on either the control-flow or data stacks are unavailable. Second, in cases where orig and dest are used, explicit pairing rules are documented on the assumption that all systems will implement that model so that its results are equivalent to employment of some stack, and that in fact many implementations do use the data stack for this purpose. However, nothing in this Standard requires that implementations actually employ the data stack (or any other) for this purpose so long as the implied behavior of the model is maintained.