Contributions
These are all contributions and replies sorted latest first (Markdown version).
Contributions:
-
tools
[151] Getting execution semantics from nt
Request for clarification
2020-08-29 08:10:26 -
search
[150] Get execution semantics from nt
Request for clarification
2020-08-28 11:29:47 -
nestable-recognizer-sequences
[149] Nestable Recognizer Sequences
Proposal
2020-08-22 16:09:52 -
optional-ieee-754-binary-floating-point-word-set
[148] OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-21 21:03:51 -
rationale
[147] Annex A section and paragraph numbering has gone wrong
Request for clarification
2020-08-21 18:41:19 -
2020-forth-standards-meeting-agenda
[146] 2020 Forth Standards meeting agenda
Proposal
2020-08-11 21:39:27 -
testsuite
[145] Please fix word spelling in F.1 second paragraph second word.
Suggested reference implementation
2020-08-08 10:00:59 -
core, PARSE
[144] What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-01 13:42:29 -
tools, SYNONYM
[143] Does the wording of the rules imply that if you SYNONYM a word with the same name in the same wordlist and then 'look it up', you will get the old word?
Request for clarification
2020-07-26 11:22:42 -
recognizer
[142] Recognizer
Proposal
2020-07-20 20:36:30 -
core, DEFER
[141] Defer Implementation
Comment
2020-06-29 06:48:12 -
[140] Overhaul 2020: Proposals
Comment
2020-06-23 22:45:08 -
core, SMDivREM
[138] There is error in testing
Comment
2020-06-21 09:31:29 -
locals
[137] Recognizer for locals
Comment
2020-06-10 02:47:06 -
same-name-token-for-different-words
[136] Same name token for different words
Proposal
2020-06-09 16:36:22 -
core, StoD
[135] Word set of S>D word
Request for clarification
2020-05-29 10:10:51 -
tools, BracketELSE
[134] Reference implementation does not seem to cope with changes to the stack
Request for clarification
2020-04-10 23:20:57 -
wording-declare-undefined-interpretation-semantics-for-locals
[133] Wording: declare undefined interpretation semantics for locals
Proposal
2020-03-08 15:18:59 -
core, p
[132] "(" typo in a testcase
Comment
2020-02-25 23:15:38 -
recognizer-rfd-rephrase-2020
[131] Recognizer RfD rephrase 2020
Proposal
2020-02-24 09:57:56 -
core, Colon
[130] The parts of execution semantics and the calling definition
Request for clarification
2020-02-21 15:32:19 -
name-interpret-wording
[129] NAME>INTERPRET wording
Proposal
2020-02-20 09:55:14 -
better-wording-for-colon
[128] Better wording for Colon
Proposal
2020-02-06 02:14:04 -
core, WITHIN
[127] sample implementation that can also be interpreted
Suggested reference implementation
2020-02-05 20:49:51 -
input-values-other-than-true-and-false
[126] Input values other than true and false
Proposal
2020-01-11 12:07:07 -
core, RECURSE
[125] Why RECURSE is needed?
Request for clarification
2020-01-09 21:15:01 -
string, REPLACES
[124] wording - "current region" term is undefined
Comment
2019-10-29 08:16:43 -
implement
[123] license
Request for clarification
2019-10-23 11:57:39 -
clarify-find-more-classic-approach
[122] Clarify FIND, more classic approach
Proposal
2019-10-08 11:01:25 -
tools, BracketELSE
[121] Case-sensitivity independent implementation
Suggested reference implementation
2019-10-03 14:30:28 -
tools, SYNONYM
[120] Test cases for SYNONYM
Suggested Testcase
2019-10-01 18:41:26 -
tools, SYNONYM
[119] Reference implementation of SYNONYM
Suggested reference implementation
2019-10-01 18:34:20 -
tools, TRAVERSE-WORDLIST
[118] Unfindable definitions
Comment
2019-09-20 23:23:52 -
vocabulary
[117] VOCABULARY
Proposal
2019-09-18 12:32:53 -
tools, SYNONYM
[116] Reference implementation and POSTPONE
Comment
2019-09-13 09:53:48 -
remove-the-rules-of-find-
[115] Remove the “rules of FIND”
Proposal
2019-09-12 09:09:51 -
case-insensitivity
[114] Case insensitivity
Proposal
2019-09-06 18:27:48 -
cs-drop-revised-2019-08-22-
[113] CS-DROP (revised 2019-08-22)
Proposal
2019-09-06 08:24:28 -
core, IMMEDIATE
[112] Ambiguous conditions
Comment
2019-09-04 09:38:20 -
file, REFILL
[111] Ambiguous conditions
Request for clarification
2019-08-28 13:06:05 -
core, toIN
[110] Etymology of ">IN" name
Request for clarification
2019-08-26 12:25:27 -
tools
[109] description of "nt" in the standard
Request for clarification
2019-08-25 21:58:52 -
block, LIST
[108] Does LIST transfer data to any buffer?
Request for clarification
2019-08-11 15:53:04 -
[107] Search box
Comment
2019-08-10 00:39:41 -
block, LOAD
[106] Getting the block contents
Request for clarification
2019-08-10 00:37:10 -
block, EVALUATE
[105] When to set BLK to zero?
Request for clarification
2019-08-09 23:21:51 -
core
[104] GNU C RESTRICT would make sense in the standard
Suggested reference implementation
2019-08-05 17:25:38 -
core, EVALUATE
[103] SOURCE-ID and nesting EVALUATE
Request for clarification
2019-08-04 15:14:25 -
core, toIN
[102] Environment dependence of test cases
Request for clarification
2019-08-03 12:56:27 -
right-justified-text-output
[101] Right-justified text output
Proposal
2019-08-01 22:07:03 -
searching-for-right-bracket-doesn-t-return-
[100] Searching for ] (right-bracket) doesn't return ]
Proposal
2019-08-01 16:07:34 -
core, BL
[99] Test example numeric base?
Request for clarification
2019-08-01 00:27:14 -
core, POSTPONE
[98] Ambiguous condition could be removed
Comment
2019-07-19 15:08:09 -
exception, CATCH
[97] The specification of CATCH
Request for clarification
2019-07-19 14:52:07 -
core, Tick
[96] Ambiguous condition in case of undefined execution semantics
Comment
2019-07-16 15:12:55 -
core, TO
[95] Ambiguous conditions
Request for clarification
2019-07-14 09:59:48 -
executing-compilation-semantics
[94] Executing compilation semantics
Proposal
2019-07-12 04:16:14 -
tools, BracketIF
[93] POSTPONE [IF]
Request for clarification
2019-07-10 14:52:51 -
core, PARSE-NAME
[92] Etymology and naming convention issue
Comment
2019-07-09 17:08:46 -
core, BUFFERColon
[91] Address between runs
Request for clarification
2019-07-09 12:54:28 -
revise-rationale-of-buffer-
[90] Revise Rationale of Buffer:
Proposal
2019-07-06 15:45:25 -
notation
[89] What is a standard program
Comment
2019-07-03 11:42:27 -
tools, NAMEtoINTERPRET
[88] How can the zero result be used in a Standard program?
Request for clarification
2019-07-02 10:29:22 -
core, COMPILEComma
[87] Interpretation semantics
Comment
2019-06-26 12:50:14 -
tools, BracketDEFINED
[86] The case of undefined interpretation semantics
Request for clarification
2019-06-26 12:09:31 -
string, UNESCAPE
[85] Etymology and naming issue
Request for clarification
2019-06-25 09:18:19 -
core, num
[84] Cell width for numbers
Request for clarification
2019-06-22 13:42:50 -
core, EXIT
[83] execution of exit
Request for clarification
2019-06-20 16:01:08 -
notation
[82] Terminology and wording regarding "dictionary"
Request for clarification
2019-06-04 08:26:12 -
core, Plus
[81] Overflow/underflow
Request for clarification
2019-05-21 23:30:20 -
core, PlusLOOP
[80] Numeric overflow/underflow
Request for clarification
2019-05-21 03:17:42 -
core, ACCEPT
[79] Receiving a zero-length string
Request for clarification
2019-05-20 20:19:43 -
core, CHAR
[78] Behavior when no text found
Comment
2019-05-19 13:57:46 -
core, ACCEPT
[77] Behavior at end of line and end of data
Request for clarification
2019-05-11 12:15:10 -
core, QUIT
[76] The reference implementation is incorrect
Suggested reference implementation
2019-03-16 14:59:29 -
f-r-and-fr-to-support-dynamically-scoped-floating-point-variables
[75] F>R and FR> to support dynamically-scoped floating point variables
Proposal
2019-03-03 06:20:52 -
tools, BracketELSE
[74] [if] and [else] parse white space - including comments
Request for clarification
2019-02-08 15:23:02 -
case-sensitivity
[73] Case sensitivity
Proposal
2018-11-03 13:15:53 -
core, TO
[72] Should TO be findable?
Request for clarification
2018-09-22 09:05:37 -
revised-proposal-process
[71] Revised Proposal Process
Proposal
2018-09-21 06:49:42 -
search, ALSO
[70] ALSO without VOCABULARY
Request for clarification
2018-09-18 12:51:27 -
core, BUFFERColon
[69] the confusing names
Request for clarification
2018-09-11 18:09:27 -
multi-tasking-proposal
[67] Multi-Tasking Proposal
Proposal
2018-09-06 17:19:38 -
cs-drop-revised-2018-08-20-
[66] CS-DROP (revised 2018-08-20)
Proposal
2018-08-20 20:22:25 -
s-request-for-discussion-revised-2018-08-16-
[65] S( "Request for Discussion" (revised 2018-08-16)
Proposal
2018-08-17 16:27:53 -
let-us-adopt-the-gerry-jackson-test-suite-as-part-of-forth-200x
[63] Let us adopt the Gerry Jackson test suite as part of Forth 200x
Proposal
2018-07-10 14:38:46 -
xchar, XHOLD
[62] Prepend, not add
Example
2018-06-28 11:05:25 -
core, HOLDS
[61] Specification of HOLDS is ambiguous
Comment
2018-06-27 15:59:05 -
tighten-the-specification-of-synonym-version-1-
[60] Tighten the specification of SYNONYM (version 1)
Proposal
2018-06-08 10:09:18 -
[59] How to change email address
Request for clarification
2018-06-06 12:08:03 -
find-name
[58] find-name
Proposal
2018-05-25 12:26:23 -
[57] Need lock on already posted comments
Example
2018-05-24 12:28:32 -
tools, NAMEtoCOMPILE
[56] NAME>COMPILE result
Comment
2018-05-24 08:13:36 -
clarify-find
[55] Clarify FIND
Proposal
2018-05-23 17:04:29 -
tools, BracketELSE
[54] [ELSE] without preceding [IF]
Comment
2018-05-13 18:36:50 -
core, INVERT
[53] Successful test cases would be good
Suggested Testcase
2018-02-28 05:03:11 -
[52] Standard 2012 as slightly reduced version - but as Part of the Forth Bookshelf
Suggested reference implementation
2018-02-25 11:57:31 -
core, Seq
[51] Reference implementation for S\"
Suggested reference implementation
2018-01-30 08:13:52 -
core, FMDivMOD
[50] Implementing FM/MOD with SM/REM
Suggested reference implementation
2018-01-22 15:32:49 -
core, CComma
[49] Suggested reference implementation
Suggested reference implementation
2018-01-08 17:54:46 -
core, TUCK
[48] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:20:49 -
core, NIP
[47] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:20:21 -
core, HEX
[46] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:19:18 -
core, BracketCHAR
[45] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:18:19 -
core, BracketTick
[44] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:17:01 -
core, TYPE
[43] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:15:17 -
core, OVER
[42] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:13:51 -
core, TwoOVER
[41] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:13:14 -
core, TwoSWAP
[40] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:12:03 -
core, TwoDUP
[39] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:11:16 -
core, TwoDROP
[38] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:10:48 -
core, FILL
[37] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:08:55 -
exception-locals
[36] EXCEPTION LOCALs
Proposal
2017-10-28 07:04:49 -
core, PARSE-NAME
[35] Space delimiters and white space
Comment
2017-10-26 16:45:24 -
bl-rationale-is-wrong
[34] BL rationale is wrong
Proposal
2017-10-25 11:35:46 -
usage
[33] Bug in 3.4.1.3
Example
2017-10-25 11:16:43 -
the-value-of-state-should-be-restored
[32] The value of STATE should be restored
Proposal
2017-09-03 11:07:49 -
file, BIN
[31] Text mode is a bad idea for file opening
Comment
2017-08-15 16:54:05 -
string, SUBSTITUTE
[30] Case sensitivity
Request for clarification
2017-07-10 18:29:41 -
core-ext-s-should-reference-file-ext-s-
[29] Core-ext S\" should reference File-ext S\"
Proposal
2017-04-16 08:03:17 -
xchar, X-SIZE
[28] UTF-8 and Unicode codepoint maximum
Request for clarification
2017-02-14 19:53:17 -
[27] Session timer and preseving contributions
Example
2016-12-31 22:07:36 -
implementations-requiring-both-32-bit-single-floats-and-64-bit-double-floats-
[26] Implementations requiring BOTH 32 bit single floats and 64 bit double floats.
Proposal
2016-12-21 14:39:40 -
directory-experiemental-proposal
[25] Directory experiemental proposal
Proposal
2016-12-12 15:42:57 -
tools, SYNONYM
[24] Incomplete specification of SYNONYM
Comment
2016-11-22 10:02:04 -
core, ACCEPT
[23] Source of a string
Request for clarification
2016-10-01 12:47:01 -
defer-this-not-
[22] DEFER this not :-)
Proposal
2016-09-02 16:14:36 -
float
[21] Mistake in the specification of significand?
Example
2016-07-03 16:20:50 -
wlscope-wordlists-switching-made-easier
[20] WLSCOPE -- wordlists switching made easier
Proposal
2016-06-18 04:19:03 -
tools, TRAVERSE-WORDLIST
[19] TRAVERSE-WORDLIST is in the wrong word set
Comment
2016-05-22 20:03:53 -
core, UNLOOP
[18] Another use of UNLOOP
Suggested Testcase
2016-05-16 21:55:15 -
core, EVALUATE
[17] Check for evaluate SOURCE is the string itself, not a copy
Suggested Testcase
2016-03-21 02:32:54 -
usage
[16] 3.3.3.5 Input buffer: "A program shall not write into the input buffer."
Comment
2016-03-21 02:27:27 -
rationale
[15] OF implementation
Suggested reference implementation
2016-02-06 13:57:57 -
file, READ-LINE
[14] Dealing with newlines
Comment
2016-02-02 15:47:01 -
core, ENDCASE
[13] Proposal: end-case
Comment
2016-01-13 20:48:24 -
[12] Digests and Meta discussion
Example
2016-01-08 18:42:54 -
core, Tick
[11]
Request for clarification
2015-12-25 23:32:43 -
core, EMIT
[10] emit fortified :-)
Comment
2015-12-13 19:01:24 -
core, RECURSE
[9] proposal: recurse' to complement recurse
Comment
2015-12-03 23:46:08 -
core, BL
[8] An example
Example
2015-11-29 23:58:06 -
core, SPACES
[7] Obvious implementation
Example
2015-11-29 23:56:42 -
core, SPACE
[6] Obvious implementation
Example
2015-11-29 23:55:49 -
core, BracketCHAR
[4] Reference implementation
Suggested reference implementation
2015-11-27 23:35:05 -
core, CHAR
[3] Non-XCHAR implementation
Suggested reference implementation
2015-11-27 20:45:54 -
core, ABS
[2] Reference implementation
Suggested reference implementation
2015-11-27 19:31:02 -
core, BL
[1] ASCII version of BL
Suggested reference implementation
2015-11-27 19:14:22
Replies:
-
special-memory-access-words
Special memory access words
Proposal
2024-06-19 11:57:08 -
special-memory-access-words
Special memory access words
Proposal
2024-06-19 08:30:04 -
special-memory-access-words
Special memory access words
Proposal
2024-06-18 21:19:30 -
special-memory-access-words
Special memory access words
Proposal
2024-06-18 17:32:06 -
special-memory-access-words
Special memory access words
Proposal
2024-06-18 13:50:08 -
support-for-single-line-comments-during-evaluate-
Support for single line comments during `evaluate`
Proposal
2024-06-18 08:15:46 -
special-memory-access-words
Special memory access words
Proposal
2024-06-18 07:50:22 -
support-for-single-line-comments-during-evaluate-
Support for single line comments during `evaluate`
Proposal
2024-06-18 07:17:32 -
obsolescence-for-save-input-and-restore-input
Obsolescence for SAVE-INPUT and RESTORE-INPUT
Proposal
2024-06-17 19:42:29 -
special-memory-access-words
Special memory access words
Proposal
2024-06-17 17:37:58 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2024-06-17 17:35:59 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2024-06-17 17:06:40 -
special-memory-access-words
Special memory access words
Proposal
2024-06-17 17:03:32 -
core, CStore
Data type of a parameters in `c!`
Request for clarification
2024-06-14 12:03:42 -
fix-stack-comments-for-n-r-and-nr-
Fix stack comments for N>R and NR>
Proposal
2024-06-06 17:05:04 -
core, Plus
Usage of the `n|u` data type
Request for clarification
2024-06-05 16:49:53 -
usage
Data object notion usage
Comment
2024-06-05 16:25:57 -
core, Plus
Usage of the `n|u` data type
Request for clarification
2024-06-04 16:01:55 -
usage
Data object notion usage
Comment
2024-06-04 15:40:50 -
string, SEARCH
Possible Reference Implementation
Suggested reference implementation
2024-06-03 15:04:14 -
core, Plus
Usage of the `n|u` data type
Request for clarification
2024-06-02 05:19:13 -
notation
Data space seems to be used invonsistently when comparing the definitions of "character string" and "data space".
Request for clarification
2024-05-30 17:31:47 -
notation
Data space seems to be used invonsistently when comparing the definitions of "character string" and "data space".
Request for clarification
2024-05-30 11:49:16 -
string, SEARCH
Possible Reference Implementation
Suggested reference implementation
2024-05-24 15:21:35 -
core, UNLOOP
Is it possible to eliminate the need for `UNLOOP`?
Request for clarification
2024-05-14 11:11:18 -
core, UNLOOP
Is it possible to eliminate the need for `UNLOOP`?
Request for clarification
2024-05-14 06:26:27 -
core, UNLOOP
Is it possible to eliminate the need for `UNLOOP`?
Request for clarification
2024-05-13 08:35:38 -
tools, NAMEtoINTERPRET
How can the zero result be used in a Standard program?
Request for clarification
2024-03-31 19:38:14 -
tools, NAMEtoINTERPRET
How can the zero result be used in a Standard program?
Request for clarification
2024-03-30 18:46:59 -
tools, NAMEtoINTERPRET
How can the zero result be used in a Standard program?
Request for clarification
2024-03-29 00:17:32 -
core, SPACES
Behavior of `0 SPACES`
Request for clarification
2024-03-07 18:44:05 -
tools, TRAVERSE-WORDLIST
shadowed names
Request for clarification
2024-03-07 18:41:03 -
tools, TRAVERSE-WORDLIST
shadowed names
Request for clarification
2024-03-06 20:55:19 -
core, SPACES
Behavior of `0 SPACES`
Request for clarification
2024-03-06 19:19:43 -
core, SPACES
Behavior of `0 SPACES`
Request for clarification
2024-03-05 06:29:23 -
core, SPACES
Behavior of `0 SPACES`
Request for clarification
2024-03-04 15:22:29 -
The Standard page does not show Chapters 1-5
Request for clarification
2024-02-19 14:13:09 -
The Standard page does not show Chapters 1-5
Request for clarification
2024-02-19 08:57:12 -
block, bs
"... the remainder of the current line."?
Request for clarification
2024-02-16 07:25:34 -
the-value-of-state-should-be-restored
The value of STATE should be restored
Proposal
2024-02-16 07:10:00 -
s-request-for-discussion-revised-2018-08-16-
S( "Request for Discussion" (revised 2018-08-16)
Proposal
2024-02-16 06:47:19 -
vocabulary
VOCABULARY
Proposal
2024-02-09 05:51:36 -
vocabulary
VOCABULARY
Proposal
2024-02-08 18:09:38 -
core, LSHIFT
An ambiguous condition in LSHIFT
Request for clarification
2024-02-06 13:47:14 -
core, LSHIFT
An ambiguous condition in LSHIFT
Request for clarification
2024-02-06 13:43:01 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-02-06 08:07:14 -
core, WORD
WORD and the text interpreter
Request for clarification
2024-02-06 07:17:25 -
core, LSHIFT
An ambiguous condition in LSHIFT
Request for clarification
2024-02-05 16:12:39 -
core, WORD
WORD and the text interpreter
Request for clarification
2024-02-02 12:07:43 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-01-31 23:49:56 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-01-31 22:44:27 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-01-31 21:34:30 -
core, DO
loopsys in data?
Request for clarification
2024-01-31 20:37:24 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-01-31 19:38:28 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-01-31 19:20:17 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-01-31 18:32:54 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-01-31 16:54:43 -
core, COMPILEComma
Implementing COMPILE, via EXECUTE
Suggested reference implementation
2024-01-31 15:58:07 -
core, QUIT
INTERPRET
Suggested reference implementation
2024-01-31 14:45:46 -
core, Colon
are colon-defs supposed to be compiled in data space?
Request for clarification
2024-01-31 13:28:17 -
core, DO
loopsys in data?
Request for clarification
2024-01-31 12:35:34 -
core, VARIABLE
Possible Reference Implementation
Suggested reference implementation
2024-01-31 12:21:58 -
core, QUIT
"make the user input device the input source"
Example
2024-01-27 12:00:18 -
core, VARIABLE
Possible Reference Implementation
Suggested reference implementation
2024-01-27 11:33:51 -
core, VARIABLE
Possible Reference Implementation
Suggested reference implementation
2024-01-26 17:27:40 -
core, QUIT
"make the user input device the input source"
Example
2024-01-26 12:55:29 -
core, QUIT
"make the user input device the input source"
Example
2024-01-26 08:57:41 -
core, QUIT
"make the user input device the input source"
Example
2024-01-25 18:43:17 -
core, QUIT
"make the user input device the input source"
Example
2024-01-25 08:25:18 -
core, QUIT
"make the user input device the input source"
Example
2024-01-24 11:51:39 -
core, QUIT
"make the user input device the input source"
Example
2024-01-24 09:49:36 -
core, QUIT
"make the user input device the input source"
Example
2024-01-24 00:40:57 -
core, DO
loopsys in data?
Request for clarification
2024-01-22 09:56:20 -
core, QUIT
"make the user input device the input source"
Example
2024-01-21 18:28:35 -
core, PAD
PAD alignment
Request for clarification
2024-01-21 17:27:03 -
core, QUIT
"make the user input device the input source"
Example
2024-01-08 05:43:00 -
core, QUIT
"make the user input device the input source"
Example
2024-01-07 22:38:40 -
core, Colon
are colon-defs supposed to be compiled in data space?
Request for clarification
2024-01-06 07:54:21 -
core, COMPILEComma
throw code for compiling outside a definition
Request for clarification
2024-01-06 07:34:58 -
core, COMPILEComma
Implementing COMPILE, via EXECUTE
Suggested reference implementation
2024-01-05 09:27:20 -
cs-drop-revised-2019-08-22-
CS-DROP (revised 2019-08-22)
Proposal
2024-01-01 09:50:56 -
search, FIND
diff from CORE FIND?
Request for clarification
2024-01-01 07:56:56 -
core, QUIT
control stack clearing?
Request for clarification
2023-12-30 20:22:36 -
tools, TRAVERSE-WORDLIST
shadowed names
Request for clarification
2023-12-27 06:54:42 -
tools, TRAVERSE-WORDLIST
shadowed names
Request for clarification
2023-12-27 06:53:10 -
tools, TRAVERSE-WORDLIST
shadowed names
Request for clarification
2023-12-26 19:03:45 -
core, MARKER
WORDLIST interaction
Example
2023-12-26 18:40:31 -
tools, TRAVERSE-WORDLIST
shadowed names
Request for clarification
2023-12-26 18:32:05 -
core, MARKER
WORDLIST interaction
Example
2023-12-26 18:22:57 -
core, MARKER
WORDLIST interaction
Example
2023-12-26 09:58:48 -
core, QUIT
The reference implementation is incorrect
Suggested reference implementation
2023-12-26 09:35:13 -
core, QUIT
control stack clearing?
Request for clarification
2023-12-26 09:08:21 -
core, QUIT
control stack clearing?
Request for clarification
2023-12-25 11:07:24 -
core, QUIT
control stack clearing?
Request for clarification
2023-12-25 08:30:25 -
core, QUIT
control stack clearing?
Request for clarification
2023-12-24 22:44:43 -
core, QUIT
control stack clearing?
Request for clarification
2023-12-24 19:16:57 -
core, QUIT
control stack clearing?
Request for clarification
2023-12-24 15:58:11 -
core, QUIT
control stack clearing?
Request for clarification
2023-12-24 15:50:50 -
core, DROP
stack checking
Suggested reference implementation
2023-12-23 08:40:48 -
tools, NAMEtoINTERPRET
NAME<INTERPRET, NAME>TO, NAME<TO
Request for clarification
2023-12-20 10:34:25 -
tools, NAMEtoINTERPRET
NAME<INTERPRET, NAME>TO, NAME<TO
Request for clarification
2023-12-20 08:23:31 -
search, SET-ORDER
Negative n values
Request for clarification
2023-12-20 07:41:02 -
tools, TRAVERSE-WORDLIST
Nested invocation, ret stack
Request for clarification
2023-12-18 08:49:57 -
search, SEARCH-WORDLIST
NDCS xt
Request for clarification
2023-12-18 08:43:16 -
testsuite
F.3 Seems in Error
Comment
2023-12-10 21:27:59 -
relax-documentation-requirements-of-ambiguous-conditions
Relax documentation requirements of Ambiguous Conditions
Proposal
2023-12-01 14:30:07 -
core, WORD
WORD and the text interpreter
Request for clarification
2023-11-28 17:56:44 -
core, WORD
WORD and the text interpreter
Request for clarification
2023-11-28 12:42:17 -
string-store-and-fetch
String store and fetch
Proposal
2023-11-13 22:17:45 -
obsolescence-for-save-input-and-restore-input
Obsolescence for SAVE-INPUT and RESTORE-INPUT
Proposal
2023-11-13 20:27:07 -
obsolescence-for-save-input-and-restore-input
Obsolescence for SAVE-INPUT and RESTORE-INPUT
Proposal
2023-11-13 20:26:44 -
place-place
PLACE +PLACE
Proposal
2023-11-09 18:47:36 -
relax-documentation-requirements-of-ambiguous-conditions
Relax documentation requirements of Ambiguous Conditions
Proposal
2023-11-09 17:38:03 -
exclude-zero-from-the-data-types-that-are-identifiers
Exclude zero from the data types that are identifiers
Proposal
2023-11-09 14:28:48 -
place-place
PLACE +PLACE
Proposal
2023-11-07 09:46:37 -
exclude-zero-from-the-data-types-that-are-identifiers
Exclude zero from the data types that are identifiers
Proposal
2023-11-07 09:36:02 -
relax-documentation-requirements-of-ambiguous-conditions
Relax documentation requirements of Ambiguous Conditions
Proposal
2023-11-07 09:31:56 -
obsolescence-for-save-input-and-restore-input
Obsolescence for SAVE-INPUT and RESTORE-INPUT
Proposal
2023-11-07 09:16:20 -
Digests and Meta discussion
Example
2023-11-03 22:24:43 -
new-words-latest-name-and-latest-name-in
New words: latest-name and latest-name-in
Proposal
2023-10-31 08:45:44 -
new-words-latest-name-and-latest-name-in
New words: latest-name and latest-name-in
Proposal
2023-10-27 20:22:13 -
new-words-latest-name-and-latest-name-in
New words: latest-name and latest-name-in
Proposal
2023-10-23 11:36:02 -
tools, TRAVERSE-WORDLIST
TRAVERSE-WORDLIST must not expose the current definition
Suggested Testcase
2023-10-23 10:08:02 -
file, INCLUDED
Example
2023-10-17 04:09:53 -
core, ERASE
Example
2023-10-15 04:51:47 -
core, VARIABLE
Possible Reference Implementation
Suggested reference implementation
2023-10-15 04:45:26 -
exception, THROW
Imlementation seems wrong for the "-2" case
Suggested reference implementation
2023-10-15 04:35:04 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-10-15 02:45:07 -
include-a-revised-79-standard-specification-for-to-core-ext-
Include a revised 79-STANDARD Specification for "><" To "Core Ext"
Proposal
2023-10-15 01:27:26 -
Digests and Meta discussion
Example
2023-10-11 17:58:12 -
f-r-and-fr-to-support-dynamically-scoped-floating-point-variables
F>R and FR> to support dynamically-scoped floating point variables
Proposal
2023-10-04 12:05:48 -
tighten-the-specification-of-synonym-version-1-
A better approach for SYNONYM wording
Comment
2023-10-03 14:27:15 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-10-01 22:54:20 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-29 08:06:21 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-09-29 07:47:52 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-09-28 17:51:10 -
defer-this-not-
DEFER this not :-)
Proposal
2023-09-23 10:04:40 -
defer-this-not-
DEFER this not :-)
Proposal
2023-09-23 08:25:11 -
tighten-the-specification-of-synonym-version-1-
A better approach for SYNONYM wording
Comment
2023-09-22 22:31:29 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-09-22 18:00:09 -
tighten-the-specification-of-synonym-version-1-
A better approach for SYNONYM wording
Comment
2023-09-22 17:19:10 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-09-22 14:13:39 -
tighten-the-specification-of-synonym-version-1-
Tighten the specification of SYNONYM (version 1)
Proposal
2023-09-21 20:58:52 -
tighten-the-specification-of-synonym-version-1-
Tighten the specification of SYNONYM (version 1)
Proposal
2023-09-21 20:56:49 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-09-21 14:15:59 -
2c-and-2c-
2C! and 2C@
Proposal
2023-09-19 20:52:38 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-09-19 15:49:52 -
clarification-for-execution-token
Clarification for execution token
Proposal
2023-09-19 15:06:17 -
executing-compilation-semantics
Executing compilation semantics
Proposal
2023-09-19 06:01:13 -
formatting-spaces-in-data-type-symbols
Formatting: spaces in data type symbols
Proposal
2023-09-19 05:46:07 -
better-wording-for-data-field-term
Better wording for "data field" term
Proposal
2023-09-19 05:42:36 -
tick-and-undefined-execution-semantics
Tick and undefined execution semantics
Proposal
2023-09-18 18:41:57 -
better-wording-for-glossary-notation-
Better wording for "Glossary notation"
Proposal
2023-09-18 18:31:44 -
exclude-zero-from-the-data-types-that-are-identifiers
Exclude zero from the data types that are identifiers
Proposal
2023-09-18 06:25:26 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-18 01:21:10 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-17 23:52:08 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-17 23:29:13 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-17 16:31:14 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-16 21:32:13 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-16 02:12:54 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-16 01:08:02 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-16 00:38:53 -
input-values-other-than-true-and-false
Input values other than true and false
Proposal
2023-09-15 17:58:21 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-15 14:03:42 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-15 08:18:00 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-15 07:51:05 -
fix-stack-comments-for-n-r-and-nr-
Fix stack comments for N>R and NR>
Proposal
2023-09-14 16:42:37 -
include-a-revised-79-standard-specification-for-to-core-ext-
Include a revised 79-STANDARD Specification for "><" To "Core Ext"
Proposal
2023-09-14 15:50:33 -
obsolescence-for-save-input-and-restore-input
Obsolescence for SAVE-INPUT and RESTORE-INPUT
Proposal
2023-09-14 15:33:36 -
clarification-for-execution-token
Clarification for execution token
Proposal
2023-09-14 15:18:24 -
revert-rewording-the-term-execution-token-
Revert rewording the term "execution token"
Proposal
2023-09-14 15:17:27 -
better-wording-for-data-field-term
Better wording for "data field" term
Proposal
2023-09-14 15:06:56 -
better-wording-for-data-field-term
Better wording for "data field" term
Proposal
2023-09-14 15:01:45 -
agenda-forth-200x-interim-meeting-2020-02-18t14-00z
Agenda Forth-200x interim Meeting 2020-02-18T14:00Z
Proposal
2023-09-14 15:01:10 -
2022-standards-meeting-agenda
2022 Standards meeting agenda
Proposal
2023-09-14 15:00:57 -
agenda-forth-200x-interim-meeting-2023-02-17t15-00z
Agenda Forth-200x interim Meeting 2023-02-17T15:00Z
Proposal
2023-09-14 15:00:39 -
2023-standards-meeting-agenda-2023-09-13-to-2023-09-15-
2023 Standards meeting agenda (2023-09-13 to 2023-09-15)
Proposal
2023-09-14 14:59:17 -
emit-and-non-ascii-values
EMIT and non-ASCII values
Proposal
2023-09-14 14:55:13 -
tick-and-undefined-execution-semantics-2
Tick and undefined execution semantics - 2
Proposal
2023-09-14 14:54:03 -
2021-standards-meeting-agenda
2021 Standards meeting agenda
Proposal
2023-09-14 14:52:11 -
tick-and-undefined-execution-semantics
Tick and undefined execution semantics
Proposal
2023-09-14 14:44:03 -
tick-and-undefined-execution-semantics
Tick and undefined execution semantics
Proposal
2023-09-14 14:28:07 -
2020-forth-standards-meeting-agenda
2020 Forth Standards meeting agenda
Proposal
2023-09-14 14:11:05 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-09-14 14:05:21 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2023-09-14 13:21:08 -
clarify-find-more-classic-approach
Clarify FIND, more classic approach
Proposal
2023-09-14 13:03:55 -
case-insensitivity
Case insensitivity
Proposal
2023-09-14 13:02:16 -
f-r-and-fr-to-support-dynamically-scoped-floating-point-variables
F>R and FR> to support dynamically-scoped floating point variables
Proposal
2023-09-14 12:39:05 -
case-sensitivity
Case sensitivity
Proposal
2023-09-14 12:36:49 -
revise-rationale-of-buffer-
Revise Rationale of Buffer:
Proposal
2023-09-14 10:07:13 -
let-us-adopt-the-gerry-jackson-test-suite-as-part-of-forth-200x
Let us adopt the Gerry Jackson test suite as part of Forth 200x
Proposal
2023-09-14 10:04:02 -
case-sensitivity
Case sensitivity
Proposal
2023-09-14 10:02:18 -
tighten-the-specification-of-synonym-version-1-
Tighten the specification of SYNONYM (version 1)
Proposal
2023-09-14 09:36:46 -
directory-experiemental-proposal
Directory experiemental proposal
Proposal
2023-09-14 08:36:39 -
defer-this-not-
DEFER this not :-)
Proposal
2023-09-14 08:26:56 -
defer-this-not-
DEFER this not :-)
Proposal
2023-09-14 08:26:40 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-14 08:00:39 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-14 07:42:43 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-14 07:00:33 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-14 06:27:22 -
fix-stack-comments-for-n-r-and-nr-
Fix stack comments for N>R and NR>
Proposal
2023-09-14 05:35:33 -
update-rationale-for-sliteral
Update rationale for SLITERAL
Proposal
2023-09-14 05:19:08 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-13 20:49:55 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-13 17:02:48 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-13 10:37:35 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-13 10:32:51 -
2023-standards-meeting-agenda-2023-09-13-to-2023-09-15-
2023 Standards meeting agenda (2023-09-13 to 2023-09-15)
Proposal
2023-09-13 09:34:11 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-13 05:08:28 -
2023-standards-meeting-agenda-2023-09-13-to-2023-09-15-
2023 Standards meeting agenda (2023-09-13 to 2023-09-15)
Proposal
2023-09-13 04:35:13 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-11 20:58:32 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-09-11 20:47:25 -
minimalistic-core-api-for-recognizers
minimalistic core API for recognizers
Proposal
2023-08-08 01:11:13 -
include-a-revised-79-standard-specification-for-to-core-ext-
Include a revised 79-STANDARD Specification for "><" To "Core Ext"
Proposal
2023-08-06 17:40:19 -
include-a-revised-79-standard-specification-for-to-core-ext-
Include a revised 79-STANDARD Specification for "><" To "Core Ext"
Proposal
2023-08-05 09:10:21 -
include-a-revised-79-standard-specification-for-to-core-ext-
Include a revised 79-STANDARD Specification for "><" To "Core Ext"
Proposal
2023-08-05 04:51:11 -
implementation standards
Suggested reference implementation
2023-07-07 07:57:11 -
16-bit-memory-access
16-bit memory access
Proposal
2023-06-24 03:06:35 -
16-bit-memory-access
16-bit memory access
Proposal
2023-06-22 23:46:15 -
16-bit-memory-access
16-bit memory access
Proposal
2023-06-22 23:41:14 -
2c-and-2c-
2C! and 2C@
Proposal
2023-06-22 23:34:51 -
2c-and-2c-
2C! and 2C@
Proposal
2023-06-22 23:08:25 -
16-bit-memory-access
16-bit memory access
Proposal
2023-06-21 19:11:09 -
2c-and-2c-
2C! and 2C@
Proposal
2023-06-09 06:04:28 -
2c-and-2c-
2C! and 2C@
Proposal
2023-06-09 02:31:22 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2023-05-06 06:29:50 -
file, INCLUDED
Example
2023-05-06 00:18:05 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2023-05-06 00:17:14 -
core, EVALUATE
New Line characters in a string passed to EVALUATE
Example
2023-05-05 18:47:22 -
core, EVALUATE
New Line characters in a string passed to EVALUATE
Example
2023-05-04 20:05:47 -
file, INCLUDED
Example
2023-05-04 15:57:26 -
core, EVALUATE
New Line characters in a string passed to EVALUATE
Example
2023-05-04 07:57:51 -
file, p
Multi-line ( behavior
Request for clarification
2023-05-04 07:33:34 -
core, EVALUATE
New Line characters in a string passed to EVALUATE
Example
2023-05-03 18:19:36 -
file, p
Multi-line ( behavior
Request for clarification
2023-05-03 17:51:25 -
file, p
Multi-line ( behavior
Request for clarification
2023-05-03 16:05:32 -
file, p
Multi-line ( behavior
Request for clarification
2023-05-03 06:32:28 -
core, Sq
Forth Programmer's Handbook
Example
2023-04-15 02:12:14 -
core, Sq
Forth Programmer's Handbook
Example
2023-04-15 01:16:57 -
core, CONSTANT
Possible Reference Implementation
Suggested reference implementation
2023-03-12 20:01:11 -
core, CHAR
Behavior when no text found
Comment
2023-03-10 11:39:07 -
relax-documentation-requirements-of-ambiguous-conditions
Relax documentation requirements of Ambiguous Conditions
Proposal
2023-03-09 10:38:44 -
update-rationale-for-sliteral
Update rationale for SLITERAL
Proposal
2023-03-07 15:03:36 -
update-rationale-for-sliteral
Update rationale for SLITERAL
Proposal
2023-03-07 13:46:06 -
usage
Data object notion usage
Comment
2023-03-07 00:48:39 -
wlscope-wordlists-switching-made-easier
WLSCOPE -- wordlists switching made easier
Proposal
2023-03-06 20:54:23 -
obsolescence-for-save-input-and-restore-input
Obsolescence for SAVE-INPUT and RESTORE-INPUT
Proposal
2023-03-04 20:37:49 -
obsolescence-for-save-input-and-restore-input
Obsolescence for SAVE-INPUT and RESTORE-INPUT
Proposal
2023-03-03 07:04:18 -
core, ROLL
Example implementation for ROLL
Suggested reference implementation
2023-03-02 19:10:24 -
core, PICK
Example implementation for PICK
Suggested reference implementation
2023-03-02 17:37:13 -
core, PICK
Example implementation for PICK
Suggested reference implementation
2023-03-02 17:33:03
