core, ACCEPT

Source of a string

Request for clarification

core, BUFFERColon

the confusing names

Request for clarification

core, TO

Should TO be findable?

Request for clarification

case-sensitivity

Case sensitivity

Proposal

core, ACCEPT

Receiving a zero-length string

Request for clarification

notation

Terminology and wording regarding "dictionary"

Request for clarification

core, EXIT

execution of exit

Request for clarification

string, UNESCAPE

Etymology and naming issue

Request for clarification

tools, BracketDEFINED

The case of undefined interpretation semantics

Request for clarification

core, COMPILEComma

Interpretation semantics

Comment

notation

What is a standard program

Comment

core, BUFFERColon

Address between runs

Request for clarification

core, PARSE-NAME

Etymology and naming convention issue

Comment

tools, BracketIF

POSTPONE [IF]

Request for clarification

executing-compilation-semantics

Executing compilation semantics

Proposal

core, TO

Ambiguous conditions

Request for clarification

core, Tick

Ambiguous condition in case of undefined execution semantics

Comment

core, POSTPONE

Ambiguous condition could be removed

Comment

core, toIN

Etymology of ">IN" name

Request for clarification

file, REFILL

Ambiguous conditions

Request for clarification

core, IMMEDIATE

Ambiguous conditions

Comment

tools, SYNONYM

Reference implementation and POSTPONE

Comment

tools, TRAVERSE-WORDLIST

Unfindable definitions

Comment

tools, BracketELSE

Case-sensitivity independent implementation

Suggested reference implementation

clarify-find-more-classic-approach

Clarify FIND, more classic approach

Proposal

string, REPLACES

wording - "current region" term is undefined

Comment

better-wording-for-colon

Better wording for Colon

Proposal

name-interpret-wording

NAME>INTERPRET wording

Proposal

core, Colon

The parts of execution semantics and the calling definition

Request for clarification

core, p

"(" typo in a testcase

Comment

wording-declare-undefined-interpretation-semantics-for-locals

Wording: declare undefined interpretation semantics for locals

Proposal

core, StoD

Word set of S>D word

Request for clarification

same-name-token-for-different-words

Same name token for different words

Proposal

locals

Recognizer for locals

Comment

search

Get execution semantics from nt

Request for clarification

tools

Getting execution semantics from nt

Request for clarification

common-terminology-for-recognizers-discurse-and-specifications

Common terminology for recognizers discurse and specifications

Proposal

tick-and-undefined-execution-semantics

Tick and undefined execution semantics

Proposal

usage

Data type for strings

Comment

usage

Data object notion usage

Comment

core, TwoStore

Cells numeration in a cell-pair

Comment

usage

Size of implementation dependent data types

Request for clarification

core, LEAVE

Stack effect of LEAVE during compilation

Request for clarification

core, BracketCOMPILE

How to avoid default compilation semantics in the specification for [COMPILE]

Comment

core, CComma

Additional test for UTF-16

Suggested Testcase

core, BracketCOMPILE

A final test case for [COMPILE]

Suggested Testcase

core, POSTPONE

Portable implementation for POSTPONE

Suggested reference implementation

wording-change-for-compile-harmonization-with-terms

Wording change for "COMPILE,": harmonization with terms

Proposal

file, Sq

Implementation for «S"» via the immediacy mechanism

Request for clarification

tools, SYNONYM

Portable implementation for SYNONYM

Suggested reference implementation

core, Bracket

Why "[" is specified using immediacy?

Request for clarification

better-wording-for-data-field-term

Better wording for "data field" term

Proposal

better-wording-for-glossary-notation-

Better wording for "Glossary notation"

Proposal

usage

Same execution token

Request for clarification

core, MARKER

Ambiguous conition for MARKER

Comment

multi-tasking-proposal

Better API for multitasking

Comment

core, COMPILEComma

Implementing COMPILE, via EXECUTE

Suggested reference implementation

revert-rewording-the-term-execution-token-

Revert rewording the term "execution token"

Proposal

formatting-spaces-in-data-type-symbols

Formatting: spaces in data type symbols

Proposal

clarification-for-execution-token

Clarification for execution token

Proposal

exclude-zero-from-the-data-types-that-are-identifiers

Exclude zero from the data types that are identifiers

Proposal

core, QUIT

Should QUIT propagate exceptions?

Request for clarification

exception

Exception word set is not optional any more

Comment

Support several versions of the standard in parallel

Comment

core, RESTORE-INPUT

Address of the input buffer after RESTORE-INPUT

Request for clarification

core, RESTORE-INPUT

About behavior or RESTORE-INPUT

Comment

core, ROLL

Example implementation for ROLL

Suggested reference implementation

core, PICK

Example implementation for PICK

Suggested reference implementation

exception, THROW

Input source after THROW

Comment

obsolescence-for-save-input-and-restore-input

Obsolescence for SAVE-INPUT and RESTORE-INPUT

Proposal

update-rationale-for-sliteral

Update rationale for SLITERAL

Proposal

tighten-the-specification-of-synonym-version-1-

A better approach for SYNONYM wording

Comment

fix-stack-comments-for-n-r-and-nr-

Why do we use +n and not u in the stack diagram for n>r and nr>

Request for clarification

new-words-latest-name-and-latest-name-in

New words: latest-name and latest-name-in

Proposal

tools, TRAVERSE-WORDLIST

TRAVERSE-WORDLIST must not expose the current definition

Suggested Testcase

core, LSHIFT

An ambiguous condition in LSHIFT

Request for clarification

core, SPACES

Behavior of `0 SPACES`

Request for clarification

doc

Request for clarification

core, UNLOOP

Is it possible to eliminate the need for `UNLOOP`?

Request for clarification

core, Plus

Usage of the `n|u` data type

Request for clarification

core, CStore

Data type of a parameters in `c!`

Request for clarification

support-for-single-line-comments-during-evaluate-

Support for single line comments during `evaluate`

Proposal

allow-the-text-interpreter-to-use-word-and-the-pictured-numeric-output

Allow the text interpreter to use `WORD` and the pictured numeric output

Proposal

core, Tick

Eliminating ambiguous conditions for Tick

Request for clarification

float, REPRESENT

Behavior of `represent` when buffer length is zero

Request for clarification

locals, bColon

Stack diagram for `{:`

Request for clarification

string, DivSTRING

Unspecified ambiguous condition in /STRING

Request for clarification

usage

Temporary removing system-compilation items

Request for clarification

core, ABORT

State of other stacks after ABORT

Request for clarification

core, ELSE

Example implementation for `ELSE`

Suggested reference implementation

block, EMPTY-BUFFERS

Behavior of EMPTY-BUFFERS when BLK is nonzero

Request for clarification

core, TO

A value-flavoured variable may be immediate

Suggested Testcase

core, PARSE-NAME

Multiple WHILE

Comment

tools, NAMEtoINTERPRET

How to perform the interpretation semantics for a word

Request for clarification

incorrect-use-of-semantics-terms

Incorrect use of semantics terms

Proposal

core, MARKER

The search order and compilation word list after a marker execution

Request for clarification

tools, CODE

May `CODE` be a parsing word?

Request for clarification

tools, NAMEtoSTRING

`NAME>STRING` result is transient

Request for clarification

core, PICK

Interpretation of the top input parameter of PICK

Comment

core, RECURSE

proposal: recurse' to complement recurse

Comment

Digests and Meta discussion

Example

core, ENDCASE

Proposal: end-case

Comment

wlscope-wordlists-switching-made-easier

WLSCOPE -- wordlists switching made easier

Proposal

defer-this-not-

DEFER this not :-)

Proposal

tools, SYNONYM

Incomplete specification of SYNONYM

Comment

directory-experiemental-proposal

Directory experiemental proposal

Proposal

Session timer and preseving contributions

Example

the-value-of-state-should-be-restored

The value of STATE should be restored

Proposal

bl-rationale-is-wrong

BL rationale is wrong

Proposal

core, FILL

Suggested reference implementation

Suggested reference implementation

clarify-find

Clarify FIND

Proposal

tools, NAMEtoCOMPILE

NAME>COMPILE result

Comment

Need lock on already posted comments

Example

find-name

find-name

Proposal

tighten-the-specification-of-synonym-version-1-

Tighten the specification of SYNONYM (version 1)

Proposal

s-request-for-discussion-revised-2018-08-16-

S( "Request for Discussion" (revised 2018-08-16)

Proposal

multi-tasking-proposal

Multi-Tasking Proposal

Proposal

core, BUFFERColon

the confusing names

Request for clarification

search, ALSO

ALSO without VOCABULARY

Request for clarification

case-sensitivity

Case sensitivity

Proposal

f-r-and-fr-to-support-dynamically-scoped-floating-point-variables

F>R and FR> to support dynamically-scoped floating point variables

Proposal

core, QUIT

The reference implementation is incorrect

Suggested reference implementation

core, CHAR

Behavior when no text found

Comment

core, ACCEPT

Receiving a zero-length string

Request for clarification

core, EXIT

execution of exit

Request for clarification

tools, BracketDEFINED

The case of undefined interpretation semantics

Request for clarification

core, COMPILEComma

Interpretation semantics

Comment

tools, NAMEtoINTERPRET

How can the zero result be used in a Standard program?

Request for clarification

notation

What is a standard program

Comment

revise-rationale-of-buffer-

Revise Rationale of Buffer:

Proposal

core, BUFFERColon

Address between runs

Request for clarification

core, PARSE-NAME

Etymology and naming convention issue

Comment

tools, BracketIF

POSTPONE [IF]

Request for clarification

core, Tick

Ambiguous condition in case of undefined execution semantics

Comment

exception, CATCH

The specification of CATCH

Request for clarification

core, POSTPONE

Ambiguous condition could be removed

Comment

core, BL

Test example numeric base?

Request for clarification

core

GNU C RESTRICT would make sense in the standard

Suggested reference implementation

block, LOAD

Getting the block contents

Request for clarification

tools

description of "nt" in the standard

Request for clarification

core, IMMEDIATE

Ambiguous conditions

Comment

cs-drop-revised-2019-08-22-

CS-DROP (revised 2019-08-22)

Proposal

case-insensitivity

Case insensitivity

Proposal

remove-the-rules-of-find-

Remove the “rules of FIND”

Proposal

tools, SYNONYM

Reference implementation of SYNONYM

Suggested reference implementation

tools, SYNONYM

Test cases for SYNONYM

Suggested Testcase

clarify-find-more-classic-approach

Clarify FIND, more classic approach

Proposal

implement

license

Request for clarification

core, RECURSE

Why RECURSE is needed?

Request for clarification

core, WITHIN

sample implementation that can also be interpreted

Suggested reference implementation

better-wording-for-colon

Better wording for Colon

Proposal

name-interpret-wording

NAME>INTERPRET wording

Proposal

core, Colon

The parts of execution semantics and the calling definition

Request for clarification

recognizer-rfd-rephrase-2020

Recognizer RfD rephrase 2020

Proposal

wording-declare-undefined-interpretation-semantics-for-locals

Wording: declare undefined interpretation semantics for locals

Proposal

same-name-token-for-different-words

Same name token for different words

Proposal

locals

Recognizer for locals

Comment

core, SMDivREM

There is error in testing

Comment

recognizer

Recognizer

Proposal

core, PARSE

What happens when parse reaches the end of the parse area and the parse delimiter was not found?

Request for clarification

optional-ieee-754-binary-floating-point-word-set

OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET

Proposal

nestable-recognizer-sequences

Nestable Recognizer Sequences

Proposal

search

Get execution semantics from nt

Request for clarification

tools

Getting execution semantics from nt

Request for clarification

traverse-wordlist-does-not-find-unnamed-unfinished-definitions

Traverse-wordlist does not find unnamed/unfinished definitions

Proposal

xml-forth-standard-migration-from-latex-to-docbook

XML Forth Standard - migration from LaTeX to DocBook

Proposal

call-for-vote-ambiguous-condition-in-16-3-3

Call for Vote - Ambiguous condition in 16.3.3

Proposal

reword-the-term-execution-token-

Reword the term "execution token"

Proposal

an-alternative-to-the-recognizer-proposal

An alternative to the RECOGNIZER proposal

Proposal

minimalistic-core-api-for-recognizers

minimalistic core API for recognizers

Proposal

common-terminology-for-recognizers-discurse-and-specifications

Common terminology for recognizers discurse and specifications

Proposal

tick-and-undefined-execution-semantics

Tick and undefined execution semantics

Proposal

usage

Data type for strings

Comment

usage

Data object notion usage

Comment

core, TwoStore

Cells numeration in a cell-pair

Comment

core, POSTPONE

Needs an example of replacing COMPILE

Example

usage

Size of implementation dependent data types

Request for clarification

emit-and-non-ascii-values

EMIT and non-ASCII values

Proposal

core, LEAVE

Stack effect of LEAVE during compilation

Request for clarification

core, DEFERStore

Does the standard assume that DEFER was created with CREATE?

Request for clarification

reference-implementations-are-not-normative

Reference implementations are not normative

Proposal

core, STATE

Advantages of a Forth system with a STATE flag?

Request for clarification

core, ALLOT

ALLOT in ROMable systems

Request for clarification

exception, THROW

Throwing past DO/LOOP

Comment

core, BracketCOMPILE

How to avoid default compilation semantics in the specification for [COMPILE]

Comment

core, CComma

Additional test for UTF-16

Suggested Testcase

xchar, XC-WIDTH

Return value of XC-WIDTH for control characters

Request for clarification

right-bracket

Web site problem?

Request for clarification

core, POSTPONE

Portable implementation for POSTPONE

Suggested reference implementation

file, Sq

Implementation for «S"» via the immediacy mechanism

Request for clarification

tools, SYNONYM

Portable implementation for SYNONYM

Suggested reference implementation

string, DivSTRING

Possible Reference Implementation

Suggested reference implementation

core, Bracket

Why "[" is specified using immediacy?

Request for clarification

place-place

PLACE +PLACE

Proposal

string, CMOVE

CMOVE implementation based on MOVE

Suggested reference implementation

tick-and-undefined-execution-semantics-2

Tick and undefined execution semantics - 2

Proposal

specify-that-0-throw-pops-the-0

Specify that 0 THROW pops the 0

Proposal

better-wording-for-data-field-term

Better wording for "data field" term

Proposal

better-wording-for-glossary-notation-

Better wording for "Glossary notation"

Proposal

core, Sq

Forth Programmer's Handbook

Example

core, POSTPONE

I suggest to complete the test

Comment

testsuite

many tests appear to only assess interpretation semantics of test subjects

Suggested Testcase

core, Cq

c-addr used in stack diagrams

Request for clarification

locals

Contradiction With do-loops

Request for clarification

locals

Accessing Remaining Data Stack?

Request for clarification

search, FORTH-WORDLIST

inconsistent naming

Request for clarification

core, VARIABLE

Possible Reference Implementation

Suggested reference implementation

core, MIN

Possible Reference Implementation

Suggested reference implementation

testsuite

F.3 Seems in Error

Comment

usage

Same execution token

Request for clarification

core, RFetch

Suggested reference implementation

multi-tasking-proposal

Round-robin vs Preemptive

Example

multi-tasking-proposal

Stack Sizes?

Example

multi-tasking-proposal

Interactions with MARKER and KILL-TASK

Example

core, ColonNONAME

:NONAME Primitives

Request for clarification

multi-tasking-proposal

Better API for multitasking

Comment

core, COMPILEComma

Implementing COMPILE, via EXECUTE

Suggested reference implementation

revert-rewording-the-term-execution-token-

Revert rewording the term "execution token"

Proposal

formatting-spaces-in-data-type-symbols

Formatting: spaces in data type symbols

Proposal

clarification-for-execution-token

Clarification for execution token

Proposal

exclude-zero-from-the-data-types-that-are-identifiers

Exclude zero from the data types that are identifiers

Proposal

core, QUIT

Should QUIT propagate exceptions?

Request for clarification

exception

Exception word set is not optional any more

Comment

pronounciations

Pronounciations

Proposal

file, SOURCE-ID

Incorrect Test Pattern

Suggested Testcase

core, SAVE-INPUT

Bogus Test Case for SAVE-INPUT

Suggested Testcase

doc

Comment

relax-documentation-requirements-of-ambiguous-conditions

Relax documentation requirements of Ambiguous Conditions

Proposal

core, ROLL

Example implementation for ROLL

Suggested reference implementation

core, PICK

Example implementation for PICK

Suggested reference implementation

block, bs

"... the remainder of the current line."?

Request for clarification

tools, NtoR

Bad Stack Notation?

Comment

core, SAVE-INPUT

Is data stack required?

Request for clarification

exception, THROW

Input source after THROW

Comment

core, RECURSE

Tail call elimination

Comment

core, bs

Maybe `REFILL`?

Suggested reference implementation

obsolescence-for-save-input-and-restore-input

Obsolescence for SAVE-INPUT and RESTORE-INPUT

Proposal

update-rationale-for-sliteral

Update rationale for SLITERAL

Proposal

core, CONSTANT

Possible Reference Implementation

Suggested reference implementation

file, INCLUDED

Example

core, ERASE

Example

exception, THROW

Imlementation seems wrong for the "-2" case

Suggested reference implementation

include-a-revised-79-standard-specification-for-to-core-ext-

Include a revised 79-STANDARD Specification for "><" To "Core Ext"

Proposal

fix-stack-comments-for-n-r-and-nr-

Fix stack comments for N>R and NR>

Proposal

tighten-the-specification-of-synonym-version-1-

A better approach for SYNONYM wording

Comment

fix-stack-comments-for-n-r-and-nr-

Why do we use +n and not u in the stack diagram for n>r and nr>

Request for clarification

new-words-latest-name-and-latest-name-in

New words: latest-name and latest-name-in

Proposal

tools, TRAVERSE-WORDLIST

TRAVERSE-WORDLIST must not expose the current definition

Suggested Testcase

string-store-and-fetch

String store and fetch

Proposal

core, WORD

WORD and the text interpreter

Request for clarification

search, SEARCH-WORDLIST

NDCS xt

Request for clarification

tools, TRAVERSE-WORDLIST

shadowed names

Request for clarification

core, Colon

are colon-defs supposed to be compiled in data space?

Request for clarification

core, DO

loopsys in data?

Request for clarification

core, QUIT

INTERPRET

Suggested reference implementation

core, LSHIFT

An ambiguous condition in LSHIFT

Request for clarification

The Standard page does not show Chapters 1-5

Request for clarification

core, SPACES

Behavior of `0 SPACES`

Request for clarification

core, UNLOOP

Is it possible to eliminate the need for `UNLOOP`?

Request for clarification

notation

Data space seems to be used invonsistently when comparing the definitions of "character string" and "data space".

Request for clarification

core, Plus

Usage of the `n|u` data type

Request for clarification

special-memory-access-words

Special memory access words

Proposal

support-for-single-line-comments-during-evaluate-

Support for single line comments during `evaluate`

Proposal

allow-the-text-interpreter-to-use-word-and-the-pictured-numeric-output

Allow the text interpreter to use `WORD` and the pictured numeric output

Proposal

float, REPRESENT

Behavior of `represent` when buffer length is zero

Request for clarification

locals, bColon

Stack diagram for `{:`

Request for clarification

obsolescence-for-save-input-and-restore-input

SAVE-INPUT

Comment

string, DivSTRING

Unspecified ambiguous condition in /STRING

Request for clarification

core, LITERAL

compile semantics or compile action of literal word

Request for clarification

core, Colon

definion and use of colon-sys and nest-sys

Request for clarification

usage

Temporary removing system-compilation items

Request for clarification

core, ELSE

Resolve the forward reference orig1 using the location following the appended run-time semantics.

Comment

block, EMPTY-BUFFERS

Behavior of EMPTY-BUFFERS when BLK is nonzero

Request for clarification

core, WORD

Behavior on oversized WORD

Request for clarification

tools, NAMEtoINTERPRET

How to perform the interpretation semantics for a word

Request for clarification

incorrect-use-of-semantics-terms

Incorrect use of semantics terms

Proposal

known-undefined-word-xlerb

Known undefined word XLERB

Proposal

octal-prefix

Octal prefix

Proposal

core, qDO

Return Stack Notation Mildly Inaccurate

Request for clarification

core, ColonNONAME

where definition is compiled?

Request for clarification

tools, NAMEtoSTRING

`NAME>STRING` result is transient

Request for clarification

search, ONLY

First Tests Seem Wrong

Suggested Testcase

core, p

Can balanced () be nested inside ( and .( comments?

Request for clarification

notation

Wording on ccc prohibits \" inside S\"

Request for clarification

core, UNUSED

What should the behavior be if the system has no hard-coded limit on size?

Request for clarification

usage

3.2.1.1 vs. Double-cell integer behavior on unusual integer architectures

Request for clarification

core, OF

May OF modify the enclosing case-sys on the control stack?

Request for clarification

tools, NRfrom

Reference implementation should not use -ROT

Suggested reference implementation

core, DOES

Is it ambiguous to execute the use of does> after :NONAME or FORGET?

Request for clarification

core, Dotq

behavior on newline

Request for clarification

tools, BracketUNDEFINED

Is behavior ambiguous if a name cannot be parsed?

Request for clarification

core, ZeroEqual

Hardware zero vs all bits zero

Request for clarification

recognizer-committee-proposal-2025-09-11

Recognizer committee proposal 2025-09-11

Proposal

non-parsing-create

Non parsing CREATE

Proposal

core, PICK

Interpretation of the top input parameter of PICK

Comment

standardize-the-well-known-rot

Standardize the well-known -ROT

Proposal

standardize-the-well-known-rdrop

Standardize the well-known RDROP

Proposal