Contributions
These are all contributions and replies sorted latest first (Markdown version).
Contributions:
-
semantic-source-modes
CCC[446] Semantic Source Modes
Proposal
2026-09-01 21:49:03 -
usage
CCC[445] Revise the Two's Complement Wrap-Around Integers
Request for clarification
2026-08-16 09:01:47 -
core, CELLS
CCC[444] Inconsistent semantic description in `CELLS`
Request for clarification
2026-08-02 11:09:02 -
ai-test-proposal
CCC[443] AI Test Proposal
Proposal
2026-07-31 10:12:39 -
usage
CCC[442] Character data type subtyping
Request for clarification
2026-07-28 00:29:38 -
core, QUIT
CCC[441] What happens when "accept a line" fails
Comment
2026-07-25 05:13:53 -
tools, BYE
CCC[440] BYE Semantics Needs Clarification
Request for clarification
2026-07-24 12:57:22 -
core, toIN
CCC[439] Should the standard distinguish application interfaces from implementation interfaces?
Comment
2026-07-20 14:28:21 -
core, BASE
CCC[438] BASE exposes representation rather than abstraction
Comment
2026-07-19 22:11:19 -
core, SAVE-INPUT
CCC[437] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-18 19:38:23 -
float, FVALUE
CCC[436] Fix FVALUE reference implementation
Suggested reference implementation
2026-07-16 16:01:41 -
block, BLOCK
CCC[434] Incorrect conditional nesting in the "no unassigned blocks" case.
Comment
2026-06-19 05:37:45 -
core, DivMOD
CCC[433] "single-cell"
Comment
2026-06-16 20:16:22 -
core,
CCC[432] Broken links
Comment
2026-06-14 22:48:09 -
core, COUNT
CCC[431] "character string specification"
Request for clarification
2026-06-14 22:39:57 -
search
CCC[430] Wording in 16.3.3 Find definition names
Request for clarification
2026-06-13 08:00:01 -
memory, RESIZE
CCC[429] Resizing to/from Zero Address Units
Request for clarification
2026-05-18 19:50:35 -
word-perform
CCC[428] word PERFORM
Proposal
2026-04-23 13:03:44 -
core, UNUSED
CCC[427] Etymology of "unused"
Comment
2026-04-09 14:09:12 -
notation
CCC[426] 2.1. Definitions of terms: Control-, Float-, Exception-stacks and may be more
Request for clarification
2026-02-28 11:03:59 -
core, ENVIRONMENTq
CCC[425] Implementation Query?
Request for clarification
2026-02-20 15:44:56 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
CCC[424] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-02-12 09:39:50 -
tools, NAMEtoSTRING
CCC[423] The buffer containing c-addr u may be transient and valid until the next invocation of NAME>STRING
Request for clarification
2026-02-09 11:33:18 -
an-appendix-grouped-by-word-contexts
CCC[422] An appendix grouped by word contexts
Proposal
2026-02-08 17:05:32 -
core, ACCEPT
CCC[421] Does ACCEPT saves/restores the original input buffer pointer?
Request for clarification
2025-12-27 12:09:56 -
core, Tick
CCC[419] Testing for non-state-smartness
Suggested Testcase
2025-10-25 12:50:27 -
standardize-the-well-known-bounds
CCC[418] Standardize the well-known BOUNDS
Proposal
2025-10-10 18:32:48 -
standardize-the-well-known-rdrop
CCC[417] Standardize the well-known RDROP
Proposal
2025-10-10 16:02:13 -
standardize-the-well-known-rot
CCC[416] Standardize the well-known -ROT
Proposal
2025-10-10 14:18:47 -
facility, EKEYq
CCC[415] Formatting
Comment
2025-10-07 15:53:02 -
core, PICK
CCC[414] Interpretation of the top input parameter of PICK
Comment
2025-10-07 08:43:07 -
non-parsing-create
CCC[413] Non parsing CREATE
Proposal
2025-09-16 11:19:01 -
recognizer-committee-proposal-2025-09-11
CCC[412] Recognizer committee proposal 2025-09-11
Proposal
2025-09-12 03:56:07 -
core, PlusStore
CCC[411] reference implementation
Suggested reference implementation
2025-09-02 11:51:03 -
core, IMMEDIATE
CCC[410] Suggested test for repeated use
Suggested Testcase
2025-08-26 12:27:16 -
core, ZeroEqual
CCC[409] Hardware zero vs all bits zero
Request for clarification
2025-08-25 13:24:21 -
a-easy-visual-separator
CCC[408] A easy visual separator
Proposal
2025-08-24 15:44:45 -
file, Sq
CCC[407] Minimum number of transient string buffers
Comment
2025-08-20 19:08:03 -
tools, BracketUNDEFINED
CCC[406] Is behavior ambiguous if a name cannot be parsed?
Request for clarification
2025-08-20 12:49:54 -
core, Dotq
CCC[405] behavior on newline
Request for clarification
2025-08-20 05:00:22 -
core, num
CCC[404] Possible reference implementation
Suggested reference implementation
2025-08-18 14:54:18 -
core, DotR
CCC[403] Possible reference implementation
Suggested reference implementation
2025-08-18 12:10:38 -
core, toNUMBER
CCC[402] Possible reference implementation
Suggested reference implementation
2025-08-17 00:00:26 -
core, DOES
CCC[401] Is it ambiguous to execute the use of does> after :NONAME or FORGET?
Request for clarification
2025-08-12 19:45:30 -
double, DNEGATE
CCC[400] Possible Reference Implementation
Suggested reference implementation
2025-08-12 12:25:58 -
double, DEqual
CCC[399] d= reference implementation
Suggested reference implementation
2025-08-11 21:26:41 -
string, COMPARE
CCC[398] Possible Reference Implementation
Suggested reference implementation
2025-08-09 15:54:10 -
core, Colon
CCC[397] `?:`?
Comment
2025-08-07 14:44:10 -
CCC[396] Example in header should feature standard Forth
Comment
2025-08-06 10:23:06 -
core, TwotoR
CCC[395] Suggested implementations
Suggested reference implementation
2025-08-04 15:28:09 -
tools, NtoR
CCC[394] Enhance n>r test to validate that n>r r@ r>n sees n
Suggested Testcase
2025-08-04 14:23:53 -
tools, NRfrom
CCC[393] Reference implementation should not use -ROT
Suggested reference implementation
2025-08-04 13:11:17 -
core, OF
CCC[392] May OF modify the enclosing case-sys on the control stack?
Request for clarification
2025-08-01 21:33:04 -
core, CASE
CCC[391] Cross-reference to the suggested implementation
Suggested reference implementation
2025-08-01 16:01:48 -
float, Ftilde
CCC[390] Change F~ to F~=
Comment
2025-07-30 19:25:54 -
usage
CCC[389] 3.2.1.1 vs. Double-cell integer behavior on unusual integer architectures
Request for clarification
2025-07-30 03:21:46 -
core, DEFERFetch
CCC[388] Must the xt returned by DEFER@ have the same value as the one passed to DEFER!, or merely the same behavior?
Request for clarification
2025-07-29 20:21:10 -
core, VALUE
CCC[387] Compilation of a VALUE child word should not inline its current value
Suggested Testcase
2025-07-26 18:27:56 -
file, READ-LINE
CCC[386] Contradictory specification when u1=0 and the file position is at the end
Request for clarification
2025-07-26 07:26:00 -
core, AGAIN
CCC[385] Suggested test
Suggested Testcase
2025-07-21 02:57:44 -
core, IF
CCC[384] Typo in test
Suggested Testcase
2025-07-21 01:53:36 -
core, UNUSED
CCC[383] What should the behavior be if the system has no hard-coded limit on size?
Request for clarification
2025-07-19 01:57:17 -
notation
CCC[382] Wording on ccc prohibits \" inside S\"
Request for clarification
2025-07-02 03:31:11 -
testsuite
CCC[381] F.3.18 typo
Comment
2025-06-30 18:50:41 -
core, p
CCC[380] Can balanced () be nested inside ( and .( comments?
Request for clarification
2025-06-30 18:21:53 -
usage
CCC[379] Typo in 3.2.1.2
Comment
2025-06-30 18:01:34 -
core, toIN
CCC[378] Can This Be Set?
Request for clarification
2025-06-13 14:21:51 -
search, ONLY
CCC[377] First Tests Seem Wrong
Suggested Testcase
2025-04-23 19:58:40 -
block, BLK
CCC[376] value okf BLK if the input source is not a block
Request for clarification
2025-04-14 12:13:33 -
double, DTwoTimes
CCC[375] First test for D2*
Example
2025-03-21 13:49:08 -
tools, NAMEtoSTRING
CCC[374] `NAME>STRING` result is transient
Request for clarification
2025-01-22 16:50:21 -
core, ColonNONAME
CCC[373] where definition is compiled?
Request for clarification
2025-01-22 15:36:24 -
tools, CODE
CCC[372] May `CODE` be a parsing word?
Request for clarification
2024-12-30 17:37:44 -
core, MARKER
CCC[371] The search order and compilation word list after a marker execution
Request for clarification
2024-12-05 09:25:19 -
core, qDO
CCC[370] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-03 21:05:42 -
octal-prefix
CCC[369] Octal prefix
Proposal
2024-12-01 00:16:09 -
known-undefined-word-xlerb
CCC[368] Known undefined word XLERB
Proposal
2024-11-25 22:50:28 -
core, MTimes
CCC[367] Incorrect test case
Suggested Testcase
2024-11-03 12:19:55 -
core, TwoTimes
CCC[366] Bad test case
Example
2024-11-01 20:33:42 -
incorrect-use-of-semantics-terms
CCC[365] Incorrect use of semantics terms
Proposal
2024-09-25 18:35:27 -
tools, NAMEtoINTERPRET
CCC[364] How to perform the interpretation semantics for a word
Request for clarification
2024-09-23 15:52:38 -
core, PICK
CCC[363] Clarification on what constitutes an ambiguous condition for this word.
Request for clarification
2024-09-19 14:31:15 -
core, WORD
CCC[362] Behavior on oversized WORD
Request for clarification
2024-09-03 23:23:24 -
core, PARSE-NAME
CCC[361] Multiple WHILE
Comment
2024-08-22 16:49:37 -
core, TO
CCC[360] A value-flavoured variable may be immediate
Suggested Testcase
2024-08-13 17:03:15 -
block, EMPTY-BUFFERS
CCC[359] Behavior of EMPTY-BUFFERS when BLK is nonzero
Request for clarification
2024-08-12 13:32:06 -
core, ELSE
CCC[358] Example implementation for `ELSE`
Suggested reference implementation
2024-08-11 10:13:40 -
core, ELSE
CCC[357] Resolve the forward reference orig1 using the location following the appended run-time semantics.
Comment
2024-08-10 21:49:59 -
core, ABORT
CCC[356] State of other stacks after ABORT
Request for clarification
2024-08-08 13:37:48 -
usage
CCC[355] Temporary removing system-compilation items
Request for clarification
2024-08-05 11:19:09 -
core, Colon
CCC[354] definion and use of colon-sys and nest-sys
Request for clarification
2024-08-04 19:34:46 -
core, LITERAL
CCC[353] compile semantics or compile action of literal word
Request for clarification
2024-07-29 13:31:50 -
string, DivSTRING
CCC[352] Unspecified ambiguous condition in /STRING
Request for clarification
2024-07-28 17:17:53 -
core, bs
CCC[351] Reuse a test for SOURCE as a starting point for a reference implementation
Suggested reference implementation
2024-07-25 16:53:47 -
core, SAVE-INPUT
CCC[350] SAVE-INPUT
Comment
2024-07-10 09:40:03 -
core, Dotp
CCC[349]
Suggested reference implementation
2024-07-04 05:24:11 -
locals, bColon
CCC[348] Stack diagram for `{:`
Request for clarification
2024-07-01 12:02:00 -
float, REPRESENT
CCC[347] Behavior of `represent` when buffer length is zero
Request for clarification
2024-06-28 23:47:44 -
core, Tick
CCC[346] Eliminating ambiguous conditions for Tick
Request for clarification
2024-06-20 15:25:45 -
allow-the-text-interpreter-to-use-word-and-the-pictured-numeric-output
CCC[345] Allow the text interpreter to use `WORD` and the pictured numeric output
Proposal
2024-06-20 12:04:57 -
support-for-single-line-comments-during-evaluate-
CCC[344] Support for single line comments during `evaluate`
Proposal
2024-06-17 20:47:11 -
special-memory-access-words
CCC[343] Special memory access words
Proposal
2024-06-14 15:18:23 -
core, CStore
CCC[342] Data type of a parameters in `c!`
Request for clarification
2024-06-11 15:56:58 -
core, Plus
CCC[341] Usage of the `n|u` data type
Request for clarification
2024-06-01 15:39:34 -
notation
CCC[340] Data space seems to be used invonsistently when comparing the definitions of "character string" and "data space".
Request for clarification
2024-05-29 20:11:10 -
core, UNLOOP
CCC[339] Is it possible to eliminate the need for `UNLOOP`?
Request for clarification
2024-05-13 08:33:18 -
doc
CCC[338]
Request for clarification
2024-03-29 01:18:49 -
core, SPACES
CCC[337] Behavior of `0 SPACES`
Request for clarification
2024-03-04 14:46:42 -
CCC[336] The Standard page does not show Chapters 1-5
Request for clarification
2024-02-17 21:34:45 -
core, LSHIFT
CCC[335] An ambiguous condition in LSHIFT
Request for clarification
2024-02-05 15:46:57 -
core, QUIT
CCC[334] INTERPRET
Suggested reference implementation
2024-01-30 22:30:13 -
CCC[333] In the list of contributions and replies by a person, please link to the contribution or reply
Comment
2024-01-24 09:35:34 -
core, PAD
CCC[332] PAD alignment
Request for clarification
2024-01-20 20:26:44 -
core, DO
CCC[331] loopsys in data?
Request for clarification
2024-01-08 06:17:40 -
core, QUIT
CCC[330] "make the user input device the input source"
Example
2024-01-06 15:25:11 -
core, Colon
CCC[329] are colon-defs supposed to be compiled in data space?
Request for clarification
2024-01-05 17:07:09 -
core, COMPILEComma
CCC[328] throw code for compiling outside a definition
Request for clarification
2024-01-05 08:52:21 -
search, FIND
CCC[327] diff from CORE FIND?
Request for clarification
2023-12-31 13:04:17 -
tools, TRAVERSE-WORDLIST
CCC[326] shadowed names
Request for clarification
2023-12-26 18:09:55 -
core, MARKER
CCC[325] WORDLIST interaction
Example
2023-12-25 12:05:23 -
core, QUIT
CCC[324] control stack clearing?
Request for clarification
2023-12-24 03:10:07 -
core, DROP
CCC[323] stack checking
Suggested reference implementation
2023-12-22 22:14:01 -
search, FORTH-WORDLIST
CCC[322] at head of ORDER?
Comment
2023-12-21 17:21:11 -
tools, NAMEtoINTERPRET
CCC[321] NAME<INTERPRET, NAME>TO, NAME<TO
Request for clarification
2023-12-20 06:09:31 -
search, SET-ORDER
CCC[320] Negative n values
Request for clarification
2023-12-19 22:16:40 -
tools, TRAVERSE-WORDLIST
CCC[319] Nested invocation, ret stack
Request for clarification
2023-12-18 04:59:48 -
search, SEARCH-WORDLIST
CCC[318] NDCS xt
Request for clarification
2023-12-17 18:15:48 -
CCC[317] CfVs after committee decision
Comment
2023-12-02 10:43:31 -
CCC[316] Proposals and the document
Comment
2023-12-01 18:08:40 -
core, WORD
CCC[315] WORD and the text interpreter
Request for clarification
2023-11-27 18:02:20 -
appendix-f-doesn-t-cater-for-strings-
CCC[314] Appendix F doesn't cater for strings.
Proposal
2023-11-12 13:26:28 -
string-store-and-fetch
CCC[313] String store and fetch
Proposal
2023-11-12 13:12:55 -
tools, TRAVERSE-WORDLIST
CCC[312] TRAVERSE-WORDLIST must not expose the current definition
Suggested Testcase
2023-10-23 10:04:08 -
new-words-latest-name-and-latest-name-in
CCC[311] New words: latest-name and latest-name-in
Proposal
2023-10-23 01:13:22 -
tools, NtoR
CCC[310] Why do we use +n and not u in the stack diagram for n>r and nr>
Request for clarification
2023-09-23 01:06:43 -
comment-better-approach-for-synonym-wording
CCC[309] A better approach for SYNONYM wording
Proposal
2023-09-22 17:06:27 -
test
CCC[308] Test
Proposal
2023-09-15 08:23:13 -
fix-stack-comments-for-n-r-and-nr-
CCC[307] Fix stack comments for N>R and NR>
Proposal
2023-09-13 12:09:40 -
2023-standards-meeting-agenda-2023-09-13-to-2023-09-15-
CCC[306] 2023 Standards meeting agenda (2023-09-13 to 2023-09-15)
Proposal
2023-09-10 17:16:18 -
include-a-revised-79-standard-specification-for-to-core-ext-
CCC[305] Include a revised 79-STANDARD Specification for "><" To "Core Ext"
Proposal
2023-08-04 14:24:50 -
exception, THROW
CCC[304] Imlementation seems wrong for the "-2" case
Suggested reference implementation
2023-08-03 10:30:03 -
CCC[303] implementation standards
Suggested reference implementation
2023-07-06 16:56:37 -
32-bit-memory-operators
CCC[302] 32-bit memory operators
Proposal
2023-06-19 13:37:39 -
16-bit-memory-access
CCC[301] 16-bit memory access
Proposal
2023-06-19 13:36:15 -
core, ERASE
CCC[300]
Example
2023-06-13 11:34:41 -
2c-and-2c-
CCC[299] 2C! and 2C@
Proposal
2023-06-07 01:09:02 -
file, INCLUDED
CCC[298]
Example
2023-05-04 15:23:46 -
file, p
CCC[297] Multi-line ( behavior
Request for clarification
2023-05-02 21:22:18 -
float
CCC[296] Single-float-aligned May Be Improperly Specified
Comment
2023-04-15 18:29:05 -
string, SEARCH
CCC[295] Possible Reference Implementation
Suggested reference implementation
2023-04-09 18:50:46 -
string, BLANK
CCC[294] Possible Reference Implementation
Suggested reference implementation
2023-04-09 12:41:33 -
core, CONSTANT
CCC[293] Possible Reference Implementation
Suggested reference implementation
2023-03-11 02:25:18 -
update-rationale-for-sliteral
CCC[292] Update rationale for SLITERAL
Proposal
2023-03-06 00:03:30 -
obsolescence-for-save-input-and-restore-input
CCC[291] Obsolescence for SAVE-INPUT and RESTORE-INPUT
Proposal
2023-03-02 19:04:49 -
double, DZeroEqual
CCC[290] Possible Reference Implementation
Suggested reference implementation
2023-02-24 14:39:44 -
core, bs
CCC[289] Maybe `REFILL`?
Suggested reference implementation
2023-02-23 16:26:01 -
core, RECURSE
CCC[288] Tail call elimination
Comment
2023-02-21 06:27:11 -
CCC[287] Overhaul 2022
Comment
2023-02-19 11:03:02 -
agenda-forth-200x-interim-meeting-2023-02-17t15-00z
CCC[286] Agenda Forth-200x interim Meeting 2023-02-17T15:00Z
Proposal
2023-02-17 09:06:20 -
float
CCC[285] Location of floats parsed from source
Request for clarification
2023-02-17 02:48:38 -
core, ENVIRONMENTq
CCC[284] First testcase broken
Suggested Testcase
2023-02-16 07:07:08 -
exception, THROW
CCC[283] Input source after THROW
Comment
2023-02-15 22:50:52 -
core, SAVE-INPUT
CCC[282] Is data stack required?
Request for clarification
2023-02-14 20:17:30 -
tools, NtoR
CCC[281] Bad Stack Notation?
Comment
2023-02-13 15:22:04 -
block, LOAD
CCC[280] Possible Test Case
Suggested Testcase
2023-02-11 16:39:10 -
block, bs
CCC[279] "... the remainder of the current line."?
Request for clarification
2023-02-11 16:04:29 -
block, THRU
CCC[278] Possible Reference Implementation
Suggested reference implementation
2023-02-11 15:56:14 -
core, PICK
CCC[277] Example implementation for PICK
Suggested reference implementation
2023-02-10 21:51:27 -
core, ROLL
CCC[276] Example implementation for ROLL
Suggested reference implementation
2023-02-10 21:32:22 -
core, RESTORE-INPUT
CCC[275] About behavior or RESTORE-INPUT
Comment
2023-02-07 16:09:01 -
core, RESTORE-INPUT
CCC[274] Address of the input buffer after RESTORE-INPUT
Request for clarification
2023-02-07 10:03:28 -
core, d
CCC[273]
Suggested reference implementation
2023-01-12 08:26:50 -
relax-documentation-requirements-of-ambiguous-conditions
CCC[272] Relax documentation requirements of Ambiguous Conditions
Proposal
2022-12-29 19:25:35 -
doc
CCC[271]
Comment
2022-12-21 11:40:45 -
core, CHAR
CCC[270] Describe Compile time and Run time behavior
Comment
2022-11-19 09:25:07 -
2022-standards-meeting-agenda
CCC[269] 2022 Standards meeting agenda
Proposal
2022-09-08 11:32:13 -
doc
CCC[268] Seemingly contradictory ambiguous condition?
Request for clarification
2022-09-08 07:51:27 -
tools, SYNONYM
CCC[267] Etymology of SYNONYM
Comment
2022-09-07 21:15:16 -
CCC[266] Support several versions of the standard in parallel
Comment
2022-09-07 11:41:37 -
core, SAVE-INPUT
CCC[265] Bogus Test Case for SAVE-INPUT
Suggested Testcase
2022-09-06 14:36:57 -
file, SOURCE-ID
CCC[264] Incorrect Test Pattern
Suggested Testcase
2022-09-06 14:26:04 -
test-proposal
CCC[263] Test Proposal
Proposal
2022-08-28 19:24:27 -
core, toNUMBER
CCC[262] >NUMBER Test Patterns
Suggested Testcase
2022-08-28 11:10:27 -
pronounciations
CCC[261] Pronounciations
Proposal
2022-08-19 18:00:05 -
exception
CCC[260] Exception word set is not optional any more
Comment
2022-08-18 13:50:15 -
core, QUIT
CCC[259] Should QUIT propagate exceptions?
Request for clarification
2022-08-18 12:09:37 -
xchar, PlusXDivSTRING
CCC[258] Pronounciation
Comment
2022-08-15 14:07:41 -
xchar, MinusTRAILING-GARBAGE
CCC[257] Pronounciation
Comment
2022-08-15 14:04:40 -
double, DUless
CCC[256] Pronounciation
Comment
2022-08-15 13:51:36 -
float, FtoS
CCC[255] Pronounciation
Comment
2022-08-15 13:48:50 -
float, StoF
CCC[254] Pronounciation
Example
2022-08-15 13:29:09 -
xchar, XSTRINGMinus
CCC[253] Pronounciation
Comment
2022-08-14 17:47:05 -
exclude-zero-from-the-data-types-that-are-identifiers
CCC[252] Exclude zero from the data types that are identifiers
Proposal
2022-08-13 23:24:52 -
clarification-for-execution-token
CCC[251] Clarification for execution token
Proposal
2022-08-13 20:16:29 -
formatting-spaces-in-data-type-symbols
CCC[250] Formatting: spaces in data type symbols
Proposal
2022-08-12 15:04:29 -
revert-rewording-the-term-execution-token-
CCC[249] Revert rewording the term "execution token"
Proposal
2022-08-12 14:18:35 -
core, COMPILEComma
CCC[248] Implementing COMPILE, via EXECUTE
Suggested reference implementation
2022-08-12 10:21:25 -
multi-tasking-proposal
CCC[247] Better API for multitasking
Comment
2022-07-18 00:03:00 -
core, MARKER
CCC[246] Ambiguous conition for MARKER
Comment
2022-07-16 10:55:40 -
core, ColonNONAME
CCC[245] :NONAME Primitives
Request for clarification
2022-07-05 16:22:37 -
multi-tasking-proposal
CCC[244] Interactions with MARKER and KILL-TASK
Example
2022-06-25 15:54:21 -
multi-tasking-proposal
CCC[243] Stack Sizes?
Example
2022-06-25 15:38:51 -
multi-tasking-proposal
CCC[242] Round-robin vs Preemptive
Example
2022-06-25 15:26:37 -
core, ROT
CCC[241]
Suggested reference implementation
2022-06-23 21:59:20 -
core, RFetch
CCC[240]
Suggested reference implementation
2022-06-20 17:40:33 -
core, TwoTimes
CCC[239]
Suggested reference implementation
2022-06-20 17:34:22 -
usage
CCC[238] Same execution token
Request for clarification
2022-06-13 22:40:38 -
usage
CCC[237] 3.4.5 conflicts with [: … ;]
Request for clarification
2022-05-11 12:45:05 -
float, FSIN
CCC[236] Trigonmetric Functions in Forth
Request for clarification
2022-04-11 17:49:49 -
testsuite
CCC[235] F.3 Seems in Error
Comment
2022-04-08 17:45:25 -
core, ALIGN
CCC[234] Possible Reference Implementation
Example
2022-04-05 17:44:08 -
core, MIN
CCC[233] Possible Reference Implementation
Suggested reference implementation
2022-04-05 14:43:43 -
core, VARIABLE
CCC[232] Possible Reference Implementation
Suggested reference implementation
2022-04-05 14:05:53 -
core, MTimes
CCC[231] Double>
Request for clarification
2022-04-04 21:04:46 -
core, UMTimes
CCC[230] Question about final test
Request for clarification
2022-04-02 21:58:34 -
search, FORTH-WORDLIST
CCC[229] inconsistent naming
Request for clarification
2022-03-18 14:04:40 -
locals
CCC[228] Accessing Remaining Data Stack?
Request for clarification
2022-03-08 20:58:26 -
locals
CCC[227] Contradiction With do-loops
Request for clarification
2022-03-08 20:39:59 -
core, Cq
CCC[226] c-addr used in stack diagrams
Request for clarification
2022-03-06 21:06:16 -
double, DZeroEqual
CCC[225] Using a . suffix to specify a double
Comment
2022-03-05 19:45:14 -
testsuite
CCC[224] many tests appear to only assess interpretation semantics of test subjects
Suggested Testcase
2022-02-27 21:23:05 -
testsuite
CCC[223] chasing for dangling words referred to
Request for clarification
2022-02-27 20:58:46 -
testsuite
CCC[222] many tests appear to only assess interpretation semantics of test subjects
Suggested Testcase
2022-02-27 18:43:57 -
core, POSTPONE
CCC[221] I suggest to complete the test
Comment
2022-02-27 14:26:42 -
agenda-forth-200x-interim-meeting-2020-02-18t14-00z
CCC[220] Agenda Forth-200x interim Meeting 2020-02-18T14:00Z
Proposal
2022-02-15 20:00:52 -
core, Sq
CCC[219] Forth Programmer's Handbook
Example
2022-02-12 16:13:14 -
core, TwoSWAP
CCC[218] Implement with ROT
Suggested reference implementation
2022-01-28 10:17:58 -
core, EVALUATE
CCC[217] New Line characters in a string passed to EVALUATE
Example
2021-11-22 17:37:54 -
file, READ-LINE
CCC[216] Some clarifications
Comment
2021-11-01 19:19:13 -
better-wording-for-glossary-notation-
CCC[215] Better wording for "Glossary notation"
Proposal
2021-09-24 11:33:41 -
better-wording-for-data-field-term
CCC[214] Better wording for "data field" term
Proposal
2021-09-14 08:55:49 -
specify-that-0-throw-pops-the-0
CCC[213] Specify that 0 THROW pops the 0
Proposal
2021-09-11 12:25:15 -
tick-and-undefined-execution-semantics-2
CCC[212] Tick and undefined execution semantics - 2
Proposal
2021-09-08 10:15:49 -
string, CMOVE
CCC[211] CMOVE implementation based on MOVE
Suggested reference implementation
2021-09-02 10:52:45 -
2021-standards-meeting-agenda
CCC[210] 2021 Standards meeting agenda
Proposal
2021-09-01 14:46:10 -
testsuite
CCC[209] Missed-order in section F.3.10 Division
Example
2021-08-21 14:29:36 -
core, WHILE
CCC[208] There is an error in testing
Comment
2021-08-20 20:54:31 -
core, DEPTH
CCC[207] More general Testcase
Suggested Testcase
2021-08-18 13:39:23 -
place-place
CCC[206] PLACE +PLACE
Proposal
2021-07-30 11:19:29 -
core, Bracket
CCC[205] Why "[" is specified using immediacy?
Request for clarification
2021-07-14 17:47:02 -
double, TwoVALUE
CCC[204] Mistake in implementation?
Comment
2021-06-27 15:30:11 -
string, DivSTRING
CCC[203] Possible Reference Implementation
Suggested reference implementation
2021-05-21 17:58:29 -
tools, SYNONYM
CCC[202] Portable implementation for SYNONYM
Suggested reference implementation
2021-05-19 13:04:00 -
file, Sq
CCC[201] Implementation for «S"» via the immediacy mechanism
Request for clarification
2021-05-18 01:22:07 -
wording-change-for-compile-harmonization-with-terms
CCC[200] Wording change for "COMPILE,": harmonization with terms
Proposal
2021-05-15 17:53:09 -
double, DtoS
CCC[199] Inaccurate Test Cases?
Suggested Testcase
2021-05-14 20:22:32 -
core, POSTPONE
CCC[198] Portable implementation for POSTPONE
Suggested reference implementation
2021-05-06 09:19:58 -
right-bracket
CCC[197] Web site problem?
Request for clarification
2021-05-05 17:24:29 -
xchar, XC-WIDTH
CCC[196] Return value of XC-WIDTH for control characters
Request for clarification
2021-04-30 19:05:32 -
core, BracketCOMPILE
CCC[195] A final test case for [COMPILE]
Suggested Testcase
2021-04-28 23:36:43
Replies:
-
clarification-for-execution-token
[r1754] Clarification for execution token
Proposal
2026-09-08 18:27:43 -
clarification-for-execution-token
[r1753] Clarification for execution token
Proposal
2026-09-07 08:21:08 -
clarification-for-execution-token
[r1752] Clarification for execution token
Proposal
2026-09-05 21:02:34 -
tools, NtoR
[r1751] Why do we use +n and not u in the stack diagram for n>r and nr>
Request for clarification
2026-09-05 19:28:31 -
tighten-the-specification-of-synonym-version-1-
[r1750] Tighten the specification of SYNONYM (version 1)
Proposal
2026-09-05 17:20:36 -
standardize-the-well-known-bounds
[r1749] Standardize the well-known BOUNDS
Proposal
2026-09-05 13:19:22 -
semantic-source-modes
[r1748] Semantic Source Modes
Proposal
2026-09-04 19:37:12 -
clarification-for-execution-token
[r1747] Clarification for execution token
Proposal
2026-09-04 13:13:49 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1746] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-09-04 11:11:32 -
word-perform
[r1745] word PERFORM
Proposal
2026-09-04 10:56:41 -
word-perform
[r1744] word PERFORM
Proposal
2026-09-04 10:56:29 -
ai-test-proposal
[r1743] AI Test Proposal
Proposal
2026-09-04 10:34:02 -
semantic-source-modes
[r1742] Semantic Source Modes
Proposal
2026-09-04 10:32:39 -
special-memory-access-words
[r1741] Special memory access words
Proposal
2026-09-04 10:16:02 -
clarification-for-execution-token
[r1740] Clarification for execution token
Proposal
2026-09-04 08:42:57 -
exclude-zero-from-the-data-types-that-are-identifiers
[r1739] Exclude zero from the data types that are identifiers
Proposal
2026-09-03 21:09:57 -
new-words-latest-name-and-latest-name-in
[r1738] New words: latest-name and latest-name-in
Proposal
2026-09-03 16:24:26 -
test-proposal
[r1737] Test Proposal
Proposal
2026-09-03 15:38:30 -
an-appendix-grouped-by-word-contexts
[r1736] An appendix grouped by word contexts
Proposal
2026-09-03 13:47:04 -
recognizer-committee-proposal-2025-09-11
[r1735] Recognizer committee proposal 2025-09-11
Proposal
2026-09-03 08:57:22 -
test-proposal
[r1734] Test Proposal
Proposal
2026-09-03 03:58:13 -
test
[r1733] Test
Proposal
2026-09-02 20:40:25 -
test-proposal
[r1732] Test Proposal
Proposal
2026-09-02 16:37:04 -
standardize-the-well-known-bounds
[r1731] Standardize the well-known BOUNDS
Proposal
2026-09-02 16:11:43 -
recognizer-committee-proposal-2025-09-11
[r1730] Recognizer committee proposal 2025-09-11
Proposal
2026-09-02 15:50:49 -
recognizer-committee-proposal-2025-09-11
[r1725] Recognizer committee proposal 2025-09-11
Proposal
2026-09-02 14:49:26 -
recognizer-committee-proposal-2025-09-11
[r1724] Recognizer committee proposal 2025-09-11
Proposal
2026-09-02 14:48:17 -
relax-documentation-requirements-of-ambiguous-conditions
[r1723] Relax documentation requirements of Ambiguous Conditions
Proposal
2026-09-02 14:34:44 -
recognizer-committee-proposal-2025-09-11
[r1722] Recognizer committee proposal 2025-09-11
Proposal
2026-09-02 08:43:24 -
core, RECURSE
[r1721] Tail call elimination
Comment
2026-08-23 10:47:44 -
core, RECURSE
[r1720] Tail call elimination
Comment
2026-08-23 03:11:16 -
core, RECURSE
[r1719] Tail call elimination
Comment
2026-08-21 10:36:14 -
usage
[r1718] Revise the Two's Complement Wrap-Around Integers
Request for clarification
2026-08-19 14:12:10 -
exclude-zero-from-the-data-types-that-are-identifiers
[r1717] Exclude zero from the data types that are identifiers
Proposal
2026-08-17 19:10:59 -
usage
[r1716] Revise the Two's Complement Wrap-Around Integers
Request for clarification
2026-08-17 14:08:55 -
usage
[r1715] Revise the Two's Complement Wrap-Around Integers
Request for clarification
2026-08-17 12:18:38 -
core, CELLS
[r1714] Inconsistent semantic description in `CELLS`
Request for clarification
2026-08-03 23:09:32 -
tools, BYE
[r1713] BYE Semantics Needs Clarification
Request for clarification
2026-08-03 12:00:37 -
core, CELLS
[r1712] Inconsistent semantic description in `CELLS`
Request for clarification
2026-08-03 08:22:03 -
core, CELLS
[r1711] Inconsistent semantic description in `CELLS`
Request for clarification
2026-08-03 07:03:24 -
ai-test-proposal
[r1710] AI Test Proposal
Proposal
2026-07-31 10:14:27 -
test
[r1709] Test
Proposal
2026-07-31 10:06:06 -
tools, BYE
[r1708] BYE Semantics Needs Clarification
Request for clarification
2026-07-26 05:09:20 -
tools, BYE
[r1707] BYE Semantics Needs Clarification
Request for clarification
2026-07-26 03:51:54 -
tools, BYE
[r1706] BYE Semantics Needs Clarification
Request for clarification
2026-07-25 05:04:36 -
core, SAVE-INPUT
[r1705] SAVE-INPUT
Comment
2026-07-22 17:12:08 -
core, SAVE-INPUT
[r1704] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-21 16:29:13 -
core, SAVE-INPUT
[r1703] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-21 09:04:07 -
core, toIN
[r1702] Should the standard distinguish application interfaces from implementation interfaces?
Comment
2026-07-21 08:09:48 -
core, SAVE-INPUT
[r1701] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-21 08:00:42 -
core, toIN
[r1700] Should the standard distinguish application interfaces from implementation interfaces?
Comment
2026-07-21 07:45:49 -
core, BASE
[r1699] BASE exposes representation rather than abstraction
Comment
2026-07-21 07:07:16 -
core, SAVE-INPUT
[r1698] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-20 22:56:31 -
core, SAVE-INPUT
[r1697] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-20 21:06:52 -
core, BASE
[r1696] BASE exposes representation rather than abstraction
Comment
2026-07-20 20:21:46 -
core, SAVE-INPUT
[r1695] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-20 19:33:54 -
core, SAVE-INPUT
[r1694] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-20 17:46:31 -
core, SAVE-INPUT
[r1693] SAVE-INPUT
Comment
2026-07-20 13:31:28 -
core, BASE
[r1692] BASE exposes representation rather than abstraction
Comment
2026-07-20 09:07:34 -
core, SAVE-INPUT
[r1691] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-20 08:48:01 -
core, BASE
[r1690] BASE exposes representation rather than abstraction
Comment
2026-07-20 08:26:37 -
core, SAVE-INPUT
[r1689] A language standard should specify abstractions rather than mechanisms
Comment
2026-07-19 16:05:44 -
recognizer-committee-proposal-2025-09-11
[r1728] Recognizer committee proposal 2025-09-11
Proposal
2026-07-16 11:52:07 -
recognizer-committee-proposal-2025-09-11
[r1727] Recognizer committee proposal 2025-09-11
Proposal
2026-07-15 05:32:41 -
recognizer-committee-proposal-2025-09-11
[r1726] Recognizer committee proposal 2025-09-11
Proposal
2026-07-14 15:31:42 -
recognizer-committee-proposal-2025-09-11
[r1686] Recognizer committee proposal 2025-09-11
Proposal
2026-07-05 11:07:32 -
recognizer-committee-proposal-2025-09-11
[r1685] Recognizer committee proposal 2025-09-11
Proposal
2026-07-05 10:38:59 -
core, DivMOD
[r1684] "single-cell"
Comment
2026-06-17 07:34:33 -
core,
[r1683] Broken links
Comment
2026-06-17 07:16:57 -
core, COUNT
[r1682] "character string specification"
Request for clarification
2026-06-16 06:09:10 -
special-memory-access-words
[r1681] Special memory access words
Proposal
2026-06-14 22:50:21 -
search
[r1680] Wording in 16.3.3 Find definition names
Request for clarification
2026-06-14 09:11:06 -
search
[r1679] Wording in 16.3.3 Find definition names
Request for clarification
2026-06-14 04:23:46 -
non-parsing-create
[r1678] Non parsing CREATE
Proposal
2026-06-11 15:40:42 -
special-memory-access-words
[r1677] Special memory access words
Proposal
2026-06-03 13:06:38 -
clarify-find-more-classic-approach
[r1676] Clarify FIND, more classic approach
Proposal
2026-06-01 01:25:49 -
special-memory-access-words
[r1675] Special memory access words
Proposal
2026-05-20 08:57:24 -
memory, RESIZE
[r1674] Resizing to/from Zero Address Units
Request for clarification
2026-05-20 07:38:06 -
special-memory-access-words
[r1673] Special memory access words
Proposal
2026-05-19 17:28:04 -
memory, RESIZE
[r1672] Resizing to/from Zero Address Units
Request for clarification
2026-05-19 12:57:49 -
special-memory-access-words
[r1671] Special memory access words
Proposal
2026-05-19 12:44:52 -
word-perform
[r1670] word PERFORM
Proposal
2026-05-19 12:10:18 -
memory, RESIZE
[r1669] Resizing to/from Zero Address Units
Request for clarification
2026-05-19 10:32:48 -
special-memory-access-words
[r1668] Special memory access words
Proposal
2026-05-19 10:16:07 -
recognizer-committee-proposal-2025-09-11
[r1667] Recognizer committee proposal 2025-09-11
Proposal
2026-05-19 10:10:42 -
memory, RESIZE
[r1666] Resizing to/from Zero Address Units
Request for clarification
2026-05-19 05:51:40 -
memory, RESIZE
[r1665] Resizing to/from Zero Address Units
Request for clarification
2026-05-19 05:51:04 -
recognizer-committee-proposal-2025-09-11
[r1664] Recognizer committee proposal 2025-09-11
Proposal
2026-05-19 05:39:39 -
special-memory-access-words
[r1663] Special memory access words
Proposal
2026-05-19 05:29:49 -
recognizer-committee-proposal-2025-09-11
[r1662] Recognizer committee proposal 2025-09-11
Proposal
2026-05-18 18:48:02 -
special-memory-access-words
[r1661] Special memory access words
Proposal
2026-05-16 23:19:25 -
special-memory-access-words
[r1660] Special memory access words
Proposal
2026-05-13 14:23:27 -
an-appendix-grouped-by-word-contexts
[r1659] An appendix grouped by word contexts
Proposal
2026-05-12 18:04:38 -
core, DEFERFetch
[r1658] Must the xt returned by DEFER@ have the same value as the one passed to DEFER!, or merely the same behavior?
Request for clarification
2026-05-12 16:48:29 -
input-values-other-than-true-and-false
[r1657] Input values other than true and false
Proposal
2026-05-12 14:40:26 -
special-memory-access-words
[r1656] Special memory access words
Proposal
2026-05-12 11:02:00 -
special-memory-access-words
[r1655] Special memory access words
Proposal
2026-05-11 17:17:44 -
special-memory-access-words
[r1654] Special memory access words
Proposal
2026-05-07 16:49:32 -
word-perform
[r1653] word PERFORM
Proposal
2026-04-25 09:35:53 -
word-perform
[r1652] word PERFORM
Proposal
2026-04-24 05:56:59 -
new-words-latest-name-and-latest-name-in
[r1651] New words: latest-name and latest-name-in
Proposal
2026-04-01 09:16:47 -
known-undefined-word-xlerb
[r1650] Known undefined word XLERB
Proposal
2026-03-24 20:03:17 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1649] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-14 08:35:09 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1648] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-13 20:14:54 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1647] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-12 18:28:01 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1646] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-12 09:27:25 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1645] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-10 14:37:38 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1644] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-10 12:18:21 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1643] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-10 11:44:13 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1642] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-10 10:09:34 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1641] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-10 09:47:43 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1640] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-07 17:44:31 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1639] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-03 17:56:24 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1638] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-03 17:44:58 -
core, Tick
[r1637]
Request for clarification
2026-03-02 19:31:19 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1636] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-01 17:02:01 -
notation
[r1635] 2.1. Definitions of terms: Control-, Float-, Exception-stacks and may be more
Request for clarification
2026-03-01 10:32:20 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1634] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-03-01 10:10:39 -
core, ENVIRONMENTq
[r1633] Implementation Query?
Request for clarification
2026-02-28 19:50:37 -
notation
[r1632] 2.1. Definitions of terms: Control-, Float-, Exception-stacks and may be more
Request for clarification
2026-02-28 16:43:36 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1631] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-02-28 13:18:51 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1630] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-02-28 11:54:26 -
tools, NAMEtoSTRING
[r1629] The buffer containing c-addr u may be transient and valid until the next invocation of NAME>STRING
Request for clarification
2026-02-28 11:26:52 -
core, ENVIRONMENTq
[r1628] Implementation Query?
Request for clarification
2026-02-27 14:29:48 -
tools, NAMEtoSTRING
[r1627] The buffer containing c-addr u may be transient and valid until the next invocation of NAME>STRING
Request for clarification
2026-02-25 10:19:46 -
forth-standards-backward-compatibility-and-modern-state-of-the-art-words-with-their-historical-traditional-counterparts-
[r1626] Forth Standards, Backward Compatibility and modern `state of the art` words with their `historical traditional` counterparts.
Proposal
2026-02-25 10:11:18 -
core, ENVIRONMENTq
[r1625] Implementation Query?
Request for clarification
2026-02-25 09:17:11 -
recognizer-committee-proposal-2025-09-11
[r1624] Recognizer committee proposal 2025-09-11
Proposal
2026-02-20 17:43:24 -
recognizer-committee-proposal-2025-09-11
[r1623] Recognizer committee proposal 2025-09-11
Proposal
2026-02-15 18:41:37 -
recognizer-committee-proposal-2025-09-11
[r1622] Recognizer committee proposal 2025-09-11
Proposal
2026-02-13 18:54:21 -
recognizer-committee-proposal-2025-09-11
[r1621] Recognizer committee proposal 2025-09-11
Proposal
2026-02-13 17:48:25 -
recognizer-committee-proposal-2025-09-11
[r1620] Recognizer committee proposal 2025-09-11
Proposal
2026-02-13 16:11:59 -
optional-ieee-754-binary-floating-point-word-set
[r1619] OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2026-02-13 14:54:47 -
recognizer-committee-proposal-2025-09-11
[r1618] Recognizer committee proposal 2025-09-11
Proposal
2026-02-12 23:44:32 -
recognizer-committee-proposal-2025-09-11
[r1617] Recognizer committee proposal 2025-09-11
Proposal
2026-02-10 22:36:05 -
recognizer-committee-proposal-2025-09-11
[r1616] Recognizer committee proposal 2025-09-11
Proposal
2026-02-10 10:36:07 -
recognizer-committee-proposal-2025-09-11
[r1615] Recognizer committee proposal 2025-09-11
Proposal
2026-02-09 19:27:30 -
recognizer-committee-proposal-2025-09-11
[r1614] Recognizer committee proposal 2025-09-11
Proposal
2026-02-08 22:29:46 -
relax-documentation-requirements-of-ambiguous-conditions
[r1613] Relax documentation requirements of Ambiguous Conditions
Proposal
2026-02-08 12:00:23 -
new-words-latest-name-and-latest-name-in
[r1612] New words: latest-name and latest-name-in
Proposal
2026-02-01 16:37:31 -
block, LOAD
[r1611] Getting the block contents
Request for clarification
2025-12-28 19:36:55 -
block, LOAD
[r1610] Getting the block contents
Request for clarification
2025-12-28 14:41:57 -
core, ACCEPT
[r1609] Does ACCEPT saves/restores the original input buffer pointer?
Request for clarification
2025-12-27 16:07:17 -
core, ACCEPT
[r1608] Does ACCEPT saves/restores the original input buffer pointer?
Request for clarification
2025-12-27 15:20:06 -
block, LOAD
[r1607] Getting the block contents
Request for clarification
2025-12-06 18:59:40 -
block, LOAD
[r1606] Getting the block contents
Request for clarification
2025-12-05 23:24:03 -
block, LOAD
[r1605] Getting the block contents
Request for clarification
2025-12-05 23:14:20 -
core, MARKER
[r1604] The search order and compilation word list after a marker execution
Request for clarification
2025-11-05 14:48:40 -
standardize-the-well-known-rdrop
[r1603] Standardize the well-known RDROP
Proposal
2025-10-17 15:33:28 -
fix-stack-comments-for-n-r-and-nr-
[r1602] Fix stack comments for N>R and NR>
Proposal
2025-10-14 15:13:15 -
core, PICK
[r1601] Interpretation of the top input parameter of PICK
Comment
2025-10-13 18:42:49 -
octal-prefix
[r1600] Octal prefix
Proposal
2025-10-13 18:32:13 -
standardize-the-well-known-rot
[r1599] Standardize the well-known -ROT
Proposal
2025-10-12 17:13:21 -
standardize-the-well-known-rdrop
[r1598] Standardize the well-known RDROP
Proposal
2025-10-11 07:42:38 -
standardize-the-well-known-rot
[r1597] Standardize the well-known -ROT
Proposal
2025-10-11 07:18:16 -
standardize-the-well-known-rdrop
[r1596] Standardize the well-known RDROP
Proposal
2025-10-10 21:46:32 -
standardize-the-well-known-rot
[r1595] Standardize the well-known -ROT
Proposal
2025-10-10 21:06:42 -
core, PICK
[r1594] Interpretation of the top input parameter of PICK
Comment
2025-10-10 20:02:49 -
standardize-the-well-known-bounds
[r1593] Standardize the well-known BOUNDS
Proposal
2025-10-10 19:42:52 -
standardize-the-well-known-rot
[r1592] Standardize the well-known -ROT
Proposal
2025-10-10 19:09:49 -
standardize-the-well-known-rdrop
[r1591] Standardize the well-known RDROP
Proposal
2025-10-10 18:37:28 -
standardize-the-well-known-rdrop
[r1590] Standardize the well-known RDROP
Proposal
2025-10-10 18:32:13 -
standardize-the-well-known-rdrop
[r1589] Standardize the well-known RDROP
Proposal
2025-10-10 16:11:00 -
standardize-the-well-known-rot
[r1588] Standardize the well-known -ROT
Proposal
2025-10-10 15:14:13 -
core, PICK
[r1587] Interpretation of the top input parameter of PICK
Comment
2025-10-10 14:38:21 -
core, PICK
[r1586] Interpretation of the top input parameter of PICK
Comment
2025-10-10 06:54:08 -
core, PICK
[r1585] Example implementation for PICK
Suggested reference implementation
2025-10-10 06:28:39 -
core, PICK
[r1584] Example implementation for PICK
Suggested reference implementation
2025-10-09 18:59:28 -
clarification-for-execution-token
[r1583] Clarification for execution token
Proposal
2025-10-07 18:56:10 -
clarification-for-execution-token
[r1582] Clarification for execution token
Proposal
2025-10-07 13:20:53 -
core, PICK
[r1581] Interpretation of the top input parameter of PICK
Comment
2025-10-07 12:58:33 -
core, PICK
[r1580] Example implementation for PICK
Suggested reference implementation
2025-10-07 07:36:21 -
core, PICK
[r1579] Example implementation for PICK
Suggested reference implementation
2025-10-07 01:39:21 -
core, PICK
[r1578] Example implementation for PICK
Suggested reference implementation
2025-10-06 17:16:44 -
core, PICK
[r1577] Example implementation for PICK
Suggested reference implementation
2025-10-05 19:23:08 -
core, PICK
[r1576] Example implementation for PICK
Suggested reference implementation
2025-10-05 18:22:32 -
core, PICK
[r1575] Example implementation for PICK
Suggested reference implementation
2025-10-05 15:35:34 -
core, PICK
[r1574] Example implementation for PICK
Suggested reference implementation
2025-10-05 03:40:13 -
new-words-latest-name-and-latest-name-in
[r1573] New words: latest-name and latest-name-in
Proposal
2025-10-03 18:29:04 -
clarification-for-execution-token
[r1572] Clarification for execution token
Proposal
2025-10-03 07:23:55 -
clarification-for-execution-token
[r1571] Clarification for execution token
Proposal
2025-10-01 19:40:13 -
recognizer-committee-proposal-2025-09-11
[r1570] Recognizer committee proposal 2025-09-11
Proposal
2025-10-01 11:05:51 -
clarification-for-execution-token
[r1569] Clarification for execution token
Proposal
2025-09-30 20:37:51 -
clarification-for-execution-token
[r1568] Clarification for execution token
Proposal
2025-09-30 09:32:40 -
fix-stack-comments-for-n-r-and-nr-
[r1567] Fix stack comments for N>R and NR>
Proposal
2025-09-30 07:22:07 -
recognizer-committee-proposal-2025-09-11
[r1566] Recognizer committee proposal 2025-09-11
Proposal
2025-09-30 00:28:33 -
clarification-for-execution-token
[r1565] Clarification for execution token
Proposal
2025-09-29 07:12:58 -
fix-stack-comments-for-n-r-and-nr-
[r1564] Fix stack comments for N>R and NR>
Proposal
2025-09-29 05:45:56 -
revert-rewording-the-term-execution-token-
[r1563] Revert rewording the term "execution token"
Proposal
2025-09-28 22:29:10 -
clarification-for-execution-token
[r1562] Clarification for execution token
Proposal
2025-09-28 22:21:31 -
recognizer-committee-proposal-2025-09-11
[r1561] Recognizer committee proposal 2025-09-11
Proposal
2025-09-26 16:09:45 -
recognizer-committee-proposal-2025-09-11
[r1560] Recognizer committee proposal 2025-09-11
Proposal
2025-09-26 16:04:45 -
place-place
[r1559] PLACE +PLACE
Proposal
2025-09-26 09:10:26 -
new-words-latest-name-and-latest-name-in
[r1558] New words: latest-name and latest-name-in
Proposal
2025-09-26 07:59:24 -
new-words-latest-name-and-latest-name-in
[r1557] New words: latest-name and latest-name-in
Proposal
2025-09-26 07:36:57 -
non-parsing-create
[r1556] Non parsing CREATE
Proposal
2025-09-24 18:52:49 -
new-words-latest-name-and-latest-name-in
[r1555] New words: latest-name and latest-name-in
Proposal
2025-09-21 13:40:49 -
new-words-latest-name-and-latest-name-in
[r1554] New words: latest-name and latest-name-in
Proposal
2025-09-19 13:17:55 -
new-words-latest-name-and-latest-name-in
[r1553] New words: latest-name and latest-name-in
Proposal
2025-09-19 12:16:19 -
core, UNUSED
[r1552] What should the behavior be if the system has no hard-coded limit on size?
Request for clarification
2025-09-19 11:26:42 -
non-parsing-create
[r1551] Non parsing CREATE
Proposal
2025-09-17 10:03:52 -
non-parsing-create
[r1550] Non parsing CREATE
Proposal
2025-09-17 08:43:47 -
non-parsing-create
[r1549] Non parsing CREATE
Proposal
2025-09-16 17:18:37 -
non-parsing-create
[r1548] Non parsing CREATE
Proposal
2025-09-16 14:00:54 -
new-words-latest-name-and-latest-name-in
[r1547] New words: latest-name and latest-name-in
Proposal
2025-09-15 20:46:29 -
new-words-latest-name-and-latest-name-in
[r1546] New words: latest-name and latest-name-in
Proposal
2025-09-15 19:54:13 -
recognizer-committee-proposal-2025-09-11
[r1545] Recognizer committee proposal 2025-09-11
Proposal
2025-09-14 20:59:38 -
recognizer-committee-proposal-2025-09-11
[r1544] Recognizer committee proposal 2025-09-11
Proposal
2025-09-14 15:27:43 -
recognizer-committee-proposal-2025-09-11
[r1543] Recognizer committee proposal 2025-09-11
Proposal
2025-09-13 17:33:10 -
recognizer-committee-proposal-2025-09-11
[r1542] Recognizer committee proposal 2025-09-11
Proposal
2025-09-12 19:19:02 -
recognizer-committee-proposal-2025-09-11
[r1541] Recognizer committee proposal 2025-09-11
Proposal
2025-09-12 18:49:52 -
recognizer-committee-proposal-2025-09-11
[r1540] Recognizer committee proposal 2025-09-11
Proposal
2025-09-12 17:09:32 -
recognizer-committee-proposal-2025-09-11
[r1539] Recognizer committee proposal 2025-09-11
Proposal
2025-09-12 15:04:45 -
optional-ieee-754-binary-floating-point-word-set
[r1538] OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2025-09-12 10:43:18 -
tick-and-undefined-execution-semantics
[r1537] Tick and undefined execution semantics
Proposal
2025-09-12 10:18:46 -
fix-stack-comments-for-n-r-and-nr-
[r1536] Fix stack comments for N>R and NR>
Proposal
2025-09-12 09:24:31 -
recognizer-committee-proposal-2025-09-11
[r1535] Recognizer committee proposal 2025-09-11
Proposal
2025-09-12 04:05:22 -
exclude-zero-from-the-data-types-that-are-identifiers
[r1534] Exclude zero from the data types that are identifiers
Proposal
2025-09-11 16:54:20 -
exclude-zero-from-the-data-types-that-are-identifiers
[r1533] Exclude zero from the data types that are identifiers
Proposal
2025-09-11 16:27:56 -
fix-stack-comments-for-n-r-and-nr-
[r1532] Fix stack comments for N>R and NR>
Proposal
2025-09-11 16:19:26 -
special-memory-access-words
[r1531] Special memory access words
Proposal
2025-09-10 08:48:02 -
core, MIN
[r1530] Possible Reference Implementation
Suggested reference implementation
2025-09-08 12:13:22 -
string, CMOVE
[r1529] CMOVE implementation based on MOVE
Suggested reference implementation
2025-09-08 10:48:10 -
core, IMMEDIATE
[r1528] Ambiguous conditions
Comment
2025-08-31 15:57:03 -
core, ZeroEqual
[r1527] Hardware zero vs all bits zero
Request for clarification
2025-08-31 10:48:02 -
core, ZeroEqual
[r1526] Hardware zero vs all bits zero
Request for clarification
2025-08-31 10:32:09 -
core, IMMEDIATE
[r1525] Suggested test for repeated use
Suggested Testcase
2025-08-27 19:32:23 -
core, ZeroEqual
[r1524] Hardware zero vs all bits zero
Request for clarification
2025-08-27 10:52:57 -
core, ZeroEqual
[r1523] Hardware zero vs all bits zero
Request for clarification
2025-08-27 06:02:10 -
core, IMMEDIATE
[r1522] Ambiguous conditions
Comment
2025-08-26 11:32:45 -
core, IMMEDIATE
[r1521] Ambiguous conditions
Comment
2025-08-25 18:25:08 -
a-easy-visual-separator
[r1520] A easy visual separator
Proposal
2025-08-25 12:33:25 -
a-easy-visual-separator
[r1519] A easy visual separator
Proposal
2025-08-25 06:12:45 -
minimalistic-core-api-for-recognizers
[r1518] minimalistic core API for recognizers
Proposal
2025-08-22 05:01:07 -
core, DotR
[r1517] Possible reference implementation
Suggested reference implementation
2025-08-21 21:58:38 -
double, DNEGATE
[r1516] Possible Reference Implementation
Suggested reference implementation
2025-08-21 21:02:20 -
double, DNEGATE
[r1515] Possible Reference Implementation
Suggested reference implementation
2025-08-21 18:44:28 -
core, FILL
[r1514] Suggested reference implementation
Suggested reference implementation
2025-08-21 09:13:19 -
tools, BracketUNDEFINED
[r1513] Is behavior ambiguous if a name cannot be parsed?
Request for clarification
2025-08-21 08:40:17 -
core, Dotq
[r1512] behavior on newline
Request for clarification
2025-08-21 08:31:43 -
tools, BracketUNDEFINED
[r1511] Is behavior ambiguous if a name cannot be parsed?
Request for clarification
2025-08-20 15:14:58 -
core, Dotq
[r1510] behavior on newline
Request for clarification
2025-08-20 10:49:33 -
core, FILL
[r1509] Suggested reference implementation
Suggested reference implementation
2025-08-20 08:28:19 -
core, FILL
[r1508] Suggested reference implementation
Suggested reference implementation
2025-08-20 01:56:05 -
block, LOAD
[r1507] Getting the block contents
Request for clarification
2025-08-18 18:27:35 -
core, num
[r1506] Possible reference implementation
Suggested reference implementation
2025-08-18 15:32:56 -
core, d
[r1505]
Suggested reference implementation
2025-08-18 12:37:54 -
core, d
[r1504]
Suggested reference implementation
2025-08-18 12:33:12 -
core, SPACES
[r1503] Behavior of `0 SPACES`
Request for clarification
2025-08-18 12:13:44 -
new-words-latest-name-and-latest-name-in
[r1502] New words: latest-name and latest-name-in
Proposal
2025-08-18 10:11:03
