Contributions by BerndPaysan
-
core, BL
ASCII version of BL
Suggested reference implementation
-
core, ABS
Reference implementation
Suggested reference implementation
-
core, CHAR
Non-XCHAR implementation
Suggested reference implementation
-
core, BracketCHAR
Reference implementation
Suggested reference implementation
-
core, SPACE
Obvious implementation
Example
-
core, SPACES
Obvious implementation
Example
-
core, BL
An example
Example
-
usage
3.3.3.5 Input buffer: "A program shall not write into the input buffer."
Comment
-
core, EVALUATE
Check for evaluate SOURCE is the string itself, not a copy
Suggested Testcase
-
xchar, XHOLD
Prepend, not add
Example
-
remove-the-rules-of-find-
Remove the “rules of FIND”
Proposal
-
recognizer
Recognizer
Proposal
-
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
-
known-undefined-word-xlerb
Known undefined word XLERB
Proposal
Replies by BerndPaysan
-
core, BL
ASCII version of BL
Suggested reference implementation
-
wlscope-wordlists-switching-made-easier
WLSCOPE -- wordlists switching made easier
Proposal
-
core, ACCEPT
Source of a string
Request for clarification
-
directory-experiemental-proposal
Directory experiemental proposal
Proposal
-
implementations-requiring-both-32-bit-single-floats-and-64-bit-double-floats-
Implementations requiring BOTH 32 bit single floats and 64 bit double floats.
Proposal
-
xchar, X-SIZE
UTF-8 and Unicode codepoint maximum
Request for clarification
-
core-ext-s-should-reference-file-ext-s-
Core-ext S\" should reference File-ext S\"
Proposal
-
bl-rationale-is-wrong
BL rationale is wrong
Proposal
-
Standard 2012 as slightly reduced version - but as Part of the Forth Bookshelf
Suggested reference implementation
-
tools, BracketELSE
[ELSE] without preceding [IF]
Comment
-
find-name
find-name
Proposal
-
tighten-the-specification-of-synonym-version-1-
Tighten the specification of SYNONYM (version 1)
Proposal
-
core, HOLDS
Specification of HOLDS is ambiguous
Comment
-
s-request-for-discussion-revised-2018-08-16-
S( "Request for Discussion" (revised 2018-08-16)
Proposal
-
tools, BracketELSE
[if] and [else] parse white space - including comments
Request for clarification
-
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
-
tools, BracketIF
POSTPONE [IF]
Request for clarification
-
core, TO
Ambiguous conditions
Request for clarification
-
core, IMMEDIATE
Ambiguous conditions
Comment
-
case-insensitivity
Case insensitivity
Proposal
-
remove-the-rules-of-find-
Remove the “rules of FIND”
Proposal
-
tools, BracketELSE
Case-sensitivity independent implementation
Suggested reference implementation
-
input-values-other-than-true-and-false
Input values other than true and false
Proposal
-
wording-declare-undefined-interpretation-semantics-for-locals
Wording: declare undefined interpretation semantics for locals
Proposal
-
recognizer
Recognizer
Proposal
-
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
-
file, Sq
Implementation for «S"» via the immediacy mechanism
Request for clarification
-
core, WHILE
There is an error in testing
Comment
-
test-proposal
Test Proposal
Proposal
-
relax-documentation-requirements-of-ambiguous-conditions
Relax documentation requirements of Ambiguous Conditions
Proposal
-
tighten-the-specification-of-synonym-version-1-
A better approach for SYNONYM wording
Comment
-
new-words-latest-name-and-latest-name-in
New words: latest-name and latest-name-in
Proposal
-
core, Plus
Usage of the `n|u` data type
Request for clarification
-
special-memory-access-words
Special memory access words
Proposal
-
tools, NAMEtoINTERPRET
How to perform the interpretation semantics for a word
Request for clarification
-
known-undefined-word-xlerb
Known undefined word XLERB
Proposal
-
octal-prefix
Octal prefix
Proposal