Contributions by ruv
-
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
Replies by ruv
-
core, RECURSE
proposal: recurse' to complement recurse
Comment
-
core, ENDCASE
Proposal: end-case
Comment
-
wlscope-wordlists-switching-made-easier
WLSCOPE -- wordlists switching made easier
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
-
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, 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
-
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
-
core, Tick
Ambiguous condition in case of undefined execution semantics
Comment
-
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
-
tools
description of "nt" in the standard
Request for clarification
-
core, IMMEDIATE
Ambiguous conditions
Comment
-
case-insensitivity
Case insensitivity
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
-
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
-
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
ruv