Contributions
These are all contributions and replies sorted latest first (Markdown version).
Contributions:
-
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 -
core, CComma
CCC[194] Additional test for UTF-16
Suggested Testcase
2021-04-28 22:47:11 -
string, COMPARE
CCC[193] How many cells can be compared ? Must have any limit ?
Request for clarification
2021-04-25 19:52:16 -
core, BracketCOMPILE
CCC[192] How to avoid default compilation semantics in the specification for [COMPILE]
Comment
2021-04-21 09:46:05 -
exception, THROW
CCC[191] Throwing past DO/LOOP
Comment
2021-04-19 19:06:28 -
core, ALLOT
CCC[190] ALLOT in ROMable systems
Request for clarification
2021-04-18 09:07:57 -
core, STATE
CCC[189] Advantages of a Forth system with a STATE flag?
Request for clarification
2021-04-17 07:08:48 -
core, TO
CCC[188] What is the intent, purpose or meaning of TO?
Example
2021-04-17 06:23:37 -
reference-implementations-are-not-normative
CCC[187] Reference implementations are not normative
Proposal
2021-04-15 08:17:45 -
core, DEFERStore
CCC[186] Does the standard assume that DEFER was created with CREATE?
Request for clarification
2021-04-14 17:41:19 -
core, LEAVE
CCC[185] Stack effect of LEAVE during compilation
Request for clarification
2021-04-04 10:35:03 -
emit-and-non-ascii-values
CCC[184] EMIT and non-ASCII values
Proposal
2021-04-03 15:34:40 -
usage
CCC[183] Size of implementation dependent data types
Request for clarification
2021-03-30 16:05:59 -
core, num
CCC[182] Note incompatability (double v single) with some older Forth's.
Comment
2021-03-13 22:39:27 -
core, COUNT
CCC[181] Is a counted string limited to 255 chars?
Request for clarification
2021-03-10 14:50:29 -
block, BLOCK
CCC[180] Can `BLOCK` transfer from mass storage in the case when block u is already in a block buffer?
Request for clarification
2021-03-05 13:31:11 -
block, BLOCK
CCC[179] Can `BLOCK` transfer from mass storage in the case when block u is already in a block buffer?
Request for clarification
2021-03-05 13:16:46 -
locals, bColon
CCC[178] Run-Time Section is Missing Words
Comment
2021-01-23 01:10:23 -
core, POSTPONE
CCC[177] Needs an example of replacing COMPILE
Example
2021-01-22 03:42:24 -
core, Tick
CCC[176] Is Tick Immediate?
Request for clarification
2021-01-22 02:52:22 -
core, POSTPONE
CCC[175] GT1 not defined
Request for clarification
2021-01-21 06:32:53 -
memory, ALLOCATE
CCC[174] write-cell-mem undefined
Request for clarification
2021-01-13 03:56:09 -
core, BracketCOMPILE
CCC[173] Obsoleted - by what?
Request for clarification
2021-01-05 08:24:25 -
core, SOURCE
CCC[172] Relationship to block set
Example
2020-12-27 08:43:01 -
core, SOURCE-ID
CCC[171] Should this reference the optional word sets where SOURCE-ID is changed
Example
2020-12-27 08:40:17 -
exception, THROW
CCC[170] THROW: text doesn't match implementation example
Comment
2020-12-06 08:05:30 -
core, TwoStore
CCC[169] Cells numeration in a cell-pair
Comment
2020-12-01 11:21:26 -
usage
CCC[168] Data object notion usage
Comment
2020-12-01 10:58:24 -
multi-tasking-proposal
CCC[167] Query re status; and minor comments
Comment
2020-11-29 06:32:26 -
usage
CCC[166] Data type for strings
Comment
2020-11-27 07:13:33 -
search, DEFINITIONS
CCC[165] off-by-one error in reference implementation
Suggested reference implementation
2020-11-13 18:43:12 -
search, SET-ORDER
CCC[164] Typo in stack comment
Comment
2020-11-04 17:07:33 -
tick-and-undefined-execution-semantics
CCC[163] Tick and undefined execution semantics
Proposal
2020-10-29 00:28:43 -
core, MARKER
CCC[162] Extending MARKER
Request for clarification
2020-09-16 15:33:45 -
common-terminology-for-recognizers-discurse-and-specifications
CCC[161] Common terminology for recognizers discurse and specifications
Proposal
2020-09-07 13:56:43 -
minimalistic-core-api-for-recognizers
CCC[160] minimalistic core API for recognizers
Proposal
2020-09-06 09:40:07 -
an-alternative-to-the-recognizer-proposal
CCC[159] An alternative to the RECOGNIZER proposal
Proposal
2020-09-05 15:09:39 -
licence-to-use-reference-implementations
CCC[158] Licence to use reference implementations
Proposal
2020-09-03 15:13:50 -
reword-the-term-execution-token-
CCC[157] Reword the term "execution token"
Proposal
2020-09-03 11:55:03 -
interpretation-semantic-for-locals-are-undefined
CCC[156] Interpretation semantic for locals are undefined
Proposal
2020-09-02 20:57:52 -
call-for-vote-ambiguous-condition-in-16-3-3
CCC[155] Call for Vote - Ambiguous condition in 16.3.3
Proposal
2020-09-02 11:16:03 -
xml-forth-standard-migration-from-latex-to-docbook
CCC[154] XML Forth Standard - migration from LaTeX to DocBook
Proposal
2020-09-01 21:16:26 -
traverse-wordlist-does-not-find-unnamed-unfinished-definitions
CCC[153] Traverse-wordlist does not find unnamed/unfinished definitions
Proposal
2020-09-01 17:41:58 -
core, LOOP
CCC[152] Missing comma
Comment
2020-08-31 19:28:21 -
tools
CCC[151] Getting execution semantics from nt
Request for clarification
2020-08-29 08:10:26 -
search
CCC[150] Get execution semantics from nt
Request for clarification
2020-08-28 11:29:47 -
nestable-recognizer-sequences
CCC[149] Nestable Recognizer Sequences
Proposal
2020-08-22 16:09:52 -
optional-ieee-754-binary-floating-point-word-set
CCC[148] OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-21 21:03:51 -
rationale
CCC[147] Annex A section and paragraph numbering has gone wrong
Request for clarification
2020-08-21 18:41:19 -
2020-forth-standards-meeting-agenda
CCC[146] 2020 Forth Standards meeting agenda
Proposal
2020-08-11 21:39:27 -
testsuite
CCC[145] Please fix word spelling in F.1 second paragraph second word.
Suggested reference implementation
2020-08-08 10:00:59 -
core, PARSE
CCC[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
CCC[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
CCC[142] Recognizer
Proposal
2020-07-20 20:36:30 -
core, DEFER
CCC[141] Defer Implementation
Comment
2020-06-29 06:48:12 -
CCC[140] Overhaul 2020: Proposals
Comment
2020-06-23 22:45:08 -
core, SMDivREM
CCC[138] There is error in testing
Comment
2020-06-21 09:31:29 -
locals
CCC[137] Recognizer for locals
Comment
2020-06-10 02:47:06 -
same-name-token-for-different-words
CCC[136] Same name token for different words
Proposal
2020-06-09 16:36:22 -
core, StoD
CCC[135] Word set of S>D word
Request for clarification
2020-05-29 10:10:51 -
tools, BracketELSE
CCC[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
CCC[133] Wording: declare undefined interpretation semantics for locals
Proposal
2020-03-08 15:18:59 -
core, p
CCC[132] "(" typo in a testcase
Comment
2020-02-25 23:15:38 -
recognizer-rfd-rephrase-2020
CCC[131] Recognizer RfD rephrase 2020
Proposal
2020-02-24 09:57:56 -
core, Colon
CCC[130] The parts of execution semantics and the calling definition
Request for clarification
2020-02-21 15:32:19 -
name-interpret-wording
CCC[129] NAME>INTERPRET wording
Proposal
2020-02-20 09:55:14 -
better-wording-for-colon
CCC[128] Better wording for Colon
Proposal
2020-02-06 02:14:04 -
core, WITHIN
CCC[127] sample implementation that can also be interpreted
Suggested reference implementation
2020-02-05 20:49:51 -
input-values-other-than-true-and-false
CCC[126] Input values other than true and false
Proposal
2020-01-11 12:07:07 -
core, RECURSE
CCC[125] Why RECURSE is needed?
Request for clarification
2020-01-09 21:15:01 -
string, REPLACES
CCC[124] wording - "current region" term is undefined
Comment
2019-10-29 08:16:43 -
implement
CCC[123] license
Request for clarification
2019-10-23 11:57:39 -
clarify-find-more-classic-approach
CCC[122] Clarify FIND, more classic approach
Proposal
2019-10-08 11:01:25 -
tools, BracketELSE
CCC[121] Case-sensitivity independent implementation
Suggested reference implementation
2019-10-03 14:30:28 -
tools, SYNONYM
CCC[120] Test cases for SYNONYM
Suggested Testcase
2019-10-01 18:41:26 -
tools, SYNONYM
CCC[119] Reference implementation of SYNONYM
Suggested reference implementation
2019-10-01 18:34:20 -
tools, TRAVERSE-WORDLIST
CCC[118] Unfindable definitions
Comment
2019-09-20 23:23:52 -
vocabulary
CCC[117] VOCABULARY
Proposal
2019-09-18 12:32:53 -
tools, SYNONYM
CCC[116] Reference implementation and POSTPONE
Comment
2019-09-13 09:53:48 -
remove-the-rules-of-find-
CCC[115] Remove the “rules of FIND”
Proposal
2019-09-12 09:09:51 -
case-insensitivity
CCC[114] Case insensitivity
Proposal
2019-09-06 18:27:48 -
cs-drop-revised-2019-08-22-
CCC[113] CS-DROP (revised 2019-08-22)
Proposal
2019-09-06 08:24:28 -
core, IMMEDIATE
CCC[112] Ambiguous conditions
Comment
2019-09-04 09:38:20 -
file, REFILL
CCC[111] Ambiguous conditions
Request for clarification
2019-08-28 13:06:05 -
core, toIN
CCC[110] Etymology of ">IN" name
Request for clarification
2019-08-26 12:25:27 -
tools
CCC[109] description of "nt" in the standard
Request for clarification
2019-08-25 21:58:52 -
block, LIST
CCC[108] Does LIST transfer data to any buffer?
Request for clarification
2019-08-11 15:53:04 -
CCC[107] Search box
Comment
2019-08-10 00:39:41 -
block, LOAD
CCC[106] Getting the block contents
Request for clarification
2019-08-10 00:37:10 -
block, EVALUATE
CCC[105] When to set BLK to zero?
Request for clarification
2019-08-09 23:21:51 -
core
CCC[104] GNU C RESTRICT would make sense in the standard
Suggested reference implementation
2019-08-05 17:25:38 -
core, EVALUATE
CCC[103] SOURCE-ID and nesting EVALUATE
Request for clarification
2019-08-04 15:14:25 -
core, toIN
CCC[102] Environment dependence of test cases
Request for clarification
2019-08-03 12:56:27 -
right-justified-text-output
CCC[101] Right-justified text output
Proposal
2019-08-01 22:07:03 -
searching-for-right-bracket-doesn-t-return-
CCC[100] Searching for ] (right-bracket) doesn't return ]
Proposal
2019-08-01 16:07:34 -
core, BL
CCC[99] Test example numeric base?
Request for clarification
2019-08-01 00:27:14 -
core, POSTPONE
CCC[98] Ambiguous condition could be removed
Comment
2019-07-19 15:08:09 -
exception, CATCH
CCC[97] The specification of CATCH
Request for clarification
2019-07-19 14:52:07 -
core, Tick
CCC[96] Ambiguous condition in case of undefined execution semantics
Comment
2019-07-16 15:12:55 -
core, TO
CCC[95] Ambiguous conditions
Request for clarification
2019-07-14 09:59:48 -
executing-compilation-semantics
CCC[94] Executing compilation semantics
Proposal
2019-07-12 04:16:14 -
tools, BracketIF
CCC[93] POSTPONE [IF]
Request for clarification
2019-07-10 14:52:51 -
core, PARSE-NAME
CCC[92] Etymology and naming convention issue
Comment
2019-07-09 17:08:46 -
core, BUFFERColon
CCC[91] Address between runs
Request for clarification
2019-07-09 12:54:28 -
revise-rationale-of-buffer-
CCC[90] Revise Rationale of Buffer:
Proposal
2019-07-06 15:45:25 -
notation
CCC[89] What is a standard program
Comment
2019-07-03 11:42:27 -
tools, NAMEtoINTERPRET
CCC[88] How can the zero result be used in a Standard program?
Request for clarification
2019-07-02 10:29:22 -
core, COMPILEComma
CCC[87] Interpretation semantics
Comment
2019-06-26 12:50:14 -
tools, BracketDEFINED
CCC[86] The case of undefined interpretation semantics
Request for clarification
2019-06-26 12:09:31 -
string, UNESCAPE
CCC[85] Etymology and naming issue
Request for clarification
2019-06-25 09:18:19 -
core, num
CCC[84] Cell width for numbers
Request for clarification
2019-06-22 13:42:50 -
core, EXIT
CCC[83] execution of exit
Request for clarification
2019-06-20 16:01:08 -
notation
CCC[82] Terminology and wording regarding "dictionary"
Request for clarification
2019-06-04 08:26:12 -
core, Plus
CCC[81] Overflow/underflow
Request for clarification
2019-05-21 23:30:20 -
core, PlusLOOP
CCC[80] Numeric overflow/underflow
Request for clarification
2019-05-21 03:17:42 -
core, ACCEPT
CCC[79] Receiving a zero-length string
Request for clarification
2019-05-20 20:19:43 -
core, CHAR
CCC[78] Behavior when no text found
Comment
2019-05-19 13:57:46 -
core, ACCEPT
CCC[77] Behavior at end of line and end of data
Request for clarification
2019-05-11 12:15:10 -
core, QUIT
CCC[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
CCC[75] F>R and FR> to support dynamically-scoped floating point variables
Proposal
2019-03-03 06:20:52 -
tools, BracketELSE
CCC[74] [if] and [else] parse white space - including comments
Request for clarification
2019-02-08 15:23:02 -
case-sensitivity
CCC[73] Case sensitivity
Proposal
2018-11-03 13:15:53 -
core, TO
CCC[72] Should TO be findable?
Request for clarification
2018-09-22 09:05:37 -
revised-proposal-process
CCC[71] Revised Proposal Process
Proposal
2018-09-21 06:49:42 -
search, ALSO
CCC[70] ALSO without VOCABULARY
Request for clarification
2018-09-18 12:51:27 -
core, BUFFERColon
CCC[69] the confusing names
Request for clarification
2018-09-11 18:09:27 -
multi-tasking-proposal
CCC[67] Multi-Tasking Proposal
Proposal
2018-09-06 17:19:38 -
cs-drop-revised-2018-08-20-
CCC[66] CS-DROP (revised 2018-08-20)
Proposal
2018-08-20 20:22:25 -
s-request-for-discussion-revised-2018-08-16-
CCC[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
CCC[63] Let us adopt the Gerry Jackson test suite as part of Forth 200x
Proposal
2018-07-10 14:38:46 -
xchar, XHOLD
CCC[62] Prepend, not add
Example
2018-06-28 11:05:25 -
core, HOLDS
CCC[61] Specification of HOLDS is ambiguous
Comment
2018-06-27 15:59:05 -
tighten-the-specification-of-synonym-version-1-
CCC[60] Tighten the specification of SYNONYM (version 1)
Proposal
2018-06-08 10:09:18 -
CCC[59] How to change email address
Request for clarification
2018-06-06 12:08:03 -
find-name
CCC[58] find-name
Proposal
2018-05-25 12:26:23 -
CCC[57] Need lock on already posted comments
Example
2018-05-24 12:28:32 -
tools, NAMEtoCOMPILE
CCC[56] NAME>COMPILE result
Comment
2018-05-24 08:13:36 -
clarify-find
CCC[55] Clarify FIND
Proposal
2018-05-23 17:04:29 -
tools, BracketELSE
CCC[54] [ELSE] without preceding [IF]
Comment
2018-05-13 18:36:50 -
core, INVERT
CCC[53] Successful test cases would be good
Suggested Testcase
2018-02-28 05:03:11 -
CCC[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
CCC[51] Reference implementation for S\"
Suggested reference implementation
2018-01-30 08:13:52 -
core, FMDivMOD
CCC[50] Implementing FM/MOD with SM/REM
Suggested reference implementation
2018-01-22 15:32:49 -
core, CComma
CCC[49] Suggested reference implementation
Suggested reference implementation
2018-01-08 17:54:46 -
core, TUCK
CCC[48] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:20:49 -
core, NIP
CCC[47] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:20:21 -
core, HEX
CCC[46] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:19:18 -
core, BracketCHAR
CCC[45] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:18:19 -
core, BracketTick
CCC[44] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:17:01 -
core, TYPE
CCC[43] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:15:17 -
core, OVER
CCC[42] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:13:51 -
core, TwoOVER
CCC[41] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:13:14 -
core, TwoSWAP
CCC[40] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:12:03 -
core, TwoDUP
CCC[39] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:11:16 -
core, TwoDROP
CCC[38] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:10:48 -
core, FILL
CCC[37] Suggested reference implementation
Suggested reference implementation
2018-01-06 18:08:55 -
exception-locals
CCC[36] EXCEPTION LOCALs
Proposal
2017-10-28 07:04:49 -
core, PARSE-NAME
CCC[35] Space delimiters and white space
Comment
2017-10-26 16:45:24 -
bl-rationale-is-wrong
CCC[34] BL rationale is wrong
Proposal
2017-10-25 11:35:46 -
usage
CCC[33] Bug in 3.4.1.3
Example
2017-10-25 11:16:43 -
the-value-of-state-should-be-restored
CCC[32] The value of STATE should be restored
Proposal
2017-09-03 11:07:49 -
file, BIN
CCC[31] Text mode is a bad idea for file opening
Comment
2017-08-15 16:54:05 -
string, SUBSTITUTE
CCC[30] Case sensitivity
Request for clarification
2017-07-10 18:29:41 -
core-ext-s-should-reference-file-ext-s-
CCC[29] Core-ext S\" should reference File-ext S\"
Proposal
2017-04-16 08:03:17 -
xchar, X-SIZE
CCC[28] UTF-8 and Unicode codepoint maximum
Request for clarification
2017-02-14 19:53:17 -
CCC[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-
CCC[26] Implementations requiring BOTH 32 bit single floats and 64 bit double floats.
Proposal
2016-12-21 14:39:40 -
directory-experiemental-proposal
CCC[25] Directory experiemental proposal
Proposal
2016-12-12 15:42:57 -
tools, SYNONYM
CCC[24] Incomplete specification of SYNONYM
Comment
2016-11-22 10:02:04 -
core, ACCEPT
CCC[23] Source of a string
Request for clarification
2016-10-01 12:47:01 -
defer-this-not-
CCC[22] DEFER this not :-)
Proposal
2016-09-02 16:14:36 -
float
CCC[21] Mistake in the specification of significand?
Example
2016-07-03 16:20:50 -
wlscope-wordlists-switching-made-easier
CCC[20] WLSCOPE -- wordlists switching made easier
Proposal
2016-06-18 04:19:03 -
tools, TRAVERSE-WORDLIST
CCC[19] TRAVERSE-WORDLIST is in the wrong word set
Comment
2016-05-22 20:03:53 -
core, UNLOOP
CCC[18] Another use of UNLOOP
Suggested Testcase
2016-05-16 21:55:15 -
core, EVALUATE
CCC[17] Check for evaluate SOURCE is the string itself, not a copy
Suggested Testcase
2016-03-21 02:32:54 -
usage
CCC[16] 3.3.3.5 Input buffer: "A program shall not write into the input buffer."
Comment
2016-03-21 02:27:27 -
rationale
CCC[15] OF implementation
Suggested reference implementation
2016-02-06 13:57:57 -
file, READ-LINE
CCC[14] Dealing with newlines
Comment
2016-02-02 15:47:01 -
core, ENDCASE
CCC[13] Proposal: end-case
Comment
2016-01-13 20:48:24 -
CCC[12] Digests and Meta discussion
Example
2016-01-08 18:42:54 -
core, Tick
CCC[11]
Request for clarification
2015-12-25 23:32:43 -
core, EMIT
CCC[10] emit fortified :-)
Comment
2015-12-13 19:01:24 -
core, RECURSE
CCC[9] proposal: recurse' to complement recurse
Comment
2015-12-03 23:46:08 -
core, BL
CCC[8] An example
Example
2015-11-29 23:58:06 -
core, SPACES
CCC[7] Obvious implementation
Example
2015-11-29 23:56:42 -
core, SPACE
CCC[6] Obvious implementation
Example
2015-11-29 23:55:49 -
core, BracketCHAR
CCC[4] Reference implementation
Suggested reference implementation
2015-11-27 23:35:05 -
core, CHAR
CCC[3] Non-XCHAR implementation
Suggested reference implementation
2015-11-27 20:45:54 -
core, ABS
CCC[2] Reference implementation
Suggested reference implementation
2015-11-27 19:31:02 -
core, BL
CCC[1] ASCII version of BL
Suggested reference implementation
2015-11-27 19:14:22
Replies:
-
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 -
core, DOES
[r1501] Is it ambiguous to execute the use of does> after :NONAME or FORGET?
Request for clarification
2025-08-18 09:47:45 -
block, LOAD
[r1500] Getting the block contents
Request for clarification
2025-08-17 17:51:39 -
core, toNUMBER
[r1499] Possible reference implementation
Suggested reference implementation
2025-08-17 15:40:24 -
core, toNUMBER
[r1498] Possible reference implementation
Suggested reference implementation
2025-08-17 00:39:27 -
new-words-latest-name-and-latest-name-in
[r1497] New words: latest-name and latest-name-in
Proposal
2025-08-15 14:42:10 -
core, OF
[r1496] May OF modify the enclosing case-sys on the control stack?
Request for clarification
2025-08-15 13:29:00 -
core, Colon
[r1495] `?:`?
Comment
2025-08-13 13:00:47 -
double, DNEGATE
[r1494] Possible Reference Implementation
Suggested reference implementation
2025-08-12 21:26:40 -
core, DOES
[r1493] Is it ambiguous to execute the use of does> after :NONAME or FORGET?
Request for clarification
2025-08-12 20:24:53 -
core, Colon
[r1492] `?:`?
Comment
2025-08-09 17:17:51 -
core, Colon
[r1491] `?:`?
Comment
2025-08-09 16:13:21 -
string, SEARCH
[r1490] Possible Reference Implementation
Suggested reference implementation
2025-08-09 15:46:15 -
string, SEARCH
[r1489] Possible Reference Implementation
Suggested reference implementation
2025-08-09 15:30:12 -
pronounciations
[r1488] Pronounciations
Proposal
2025-08-08 18:37:48 -
minimalistic-core-api-for-recognizers
[r1487] minimalistic core API for recognizers
Proposal
2025-08-08 18:15:40 -
core, Colon
[r1486] `?:`?
Comment
2025-08-08 17:51:25 -
core, Colon
[r1485] `?:`?
Comment
2025-08-08 14:00:22 -
core, IMMEDIATE
[r1484] Ambiguous conditions
Comment
2025-08-07 18:20:42 -
core, Colon
[r1483] `?:`?
Comment
2025-08-07 15:29:04 -
core, AGAIN
[r1482] Suggested test
Suggested Testcase
2025-08-06 11:37:45 -
find-name
[r1481] find-name
Proposal
2025-08-06 06:49:26 -
core, OF
[r1480] May OF modify the enclosing case-sys on the control stack?
Request for clarification
2025-08-06 05:59:34 -
usage
[r1479] 3.2.1.1 vs. Double-cell integer behavior on unusual integer architectures
Request for clarification
2025-08-06 03:21:37 -
core, OF
[r1478] May OF modify the enclosing case-sys on the control stack?
Request for clarification
2025-08-06 02:24:08 -
tools, NRfrom
[r1477] Reference implementation should not use -ROT
Suggested reference implementation
2025-08-06 01:48:30 -
find-name
[r1476] find-name
Proposal
2025-08-06 01:34:04 -
find-name
[r1475] find-name
Proposal
2025-08-05 20:34:58 -
core, FMDivMOD
[r1474] Implementing FM/MOD with SM/REM
Suggested reference implementation
2025-08-05 01:19:19 -
tools, NRfrom
[r1473] Reference implementation should not use -ROT
Suggested reference implementation
2025-08-04 14:11:41 -
core, OF
[r1472] May OF modify the enclosing case-sys on the control stack?
Request for clarification
2025-08-02 06:06:31 -
core, OF
[r1471] May OF modify the enclosing case-sys on the control stack?
Request for clarification
2025-08-02 05:41:50 -
core, VALUE
[r1470] Compilation of a VALUE child word should not inline its current value
Suggested Testcase
2025-08-02 05:23:00 -
core, VALUE
[r1469] Compilation of a VALUE child word should not inline its current value
Suggested Testcase
2025-08-01 11:48:07 -
core, VALUE
[r1468] Compilation of a VALUE child word should not inline its current value
Suggested Testcase
2025-08-01 11:39:15 -
core, VALUE
[r1467] Compilation of a VALUE child word should not inline its current value
Suggested Testcase
2025-08-01 05:49:00 -
core, VALUE
[r1466] Compilation of a VALUE child word should not inline its current value
Suggested Testcase
2025-07-31 16:50:19 -
usage
[r1465] 3.2.1.1 vs. Double-cell integer behavior on unusual integer architectures
Request for clarification
2025-07-31 10:31:50 -
core, DEFERFetch
[r1464] 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-31 09:43:47 -
usage
[r1463] 3.2.1.1 vs. Double-cell integer behavior on unusual integer architectures
Request for clarification
2025-07-30 15:21:17 -
core, DEFERFetch
[r1462] 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-30 13:41:26 -
core, DEFERFetch
[r1461] 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-30 12:56:14 -
usage
[r1460] 3.2.1.1 vs. Double-cell integer behavior on unusual integer architectures
Request for clarification
2025-07-30 09:08:30 -
core, DEFERFetch
[r1459] 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-30 08:39:25 -
core, DEFERFetch
[r1458] 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-30 03:29:04 -
usage
[r1457] 3.2.1.1 vs. Double-cell integer behavior on unusual integer architectures
Request for clarification
2025-07-30 03:28:21 -
usage
[r1456] Same execution token
Request for clarification
2025-07-30 01:54:44 -
testsuite
[r1455] F.3.18 typo
Comment
2025-07-21 13:54:29 -
core, UNUSED
[r1454] What should the behavior be if the system has no hard-coded limit on size?
Request for clarification
2025-07-20 12:02:55 -
notation
[r1453] Wording on ccc prohibits \" inside S\"
Request for clarification
2025-07-11 13:19:49 -
notation
[r1452] Wording on ccc prohibits \" inside S\"
Request for clarification
2025-07-11 13:18:22 -
notation
[r1451] Wording on ccc prohibits \" inside S\"
Request for clarification
2025-07-02 12:09:00 -
core, p
[r1450] Can balanced () be nested inside ( and .( comments?
Request for clarification
2025-07-02 11:24:32 -
octal-prefix
[r1449] Octal prefix
Proposal
2025-07-02 05:14:37 -
octal-prefix
[r1448] Octal prefix
Proposal
2025-06-17 10:22:49 -
core, toIN
[r1447] Can This Be Set?
Request for clarification
2025-06-14 05:39:55 -
octal-prefix
[r1446] Octal prefix
Proposal
2025-05-23 15:27:07 -
search, ONLY
[r1445] First Tests Seem Wrong
Suggested Testcase
2025-04-24 16:17:52 -
block, BLK
[r1444] value okf BLK if the input source is not a block
Request for clarification
2025-04-14 21:35:36 -
minimalistic-core-api-for-recognizers
[r1443] minimalistic core API for recognizers
Proposal
2025-03-06 01:10:47 -
minimalistic-core-api-for-recognizers
[r1442] minimalistic core API for recognizers
Proposal
2025-02-26 16:36:23 -
minimalistic-core-api-for-recognizers
[r1441] minimalistic core API for recognizers
Proposal
2025-02-24 00:39:15 -
minimalistic-core-api-for-recognizers
[r1440] minimalistic core API for recognizers
Proposal
2025-02-23 16:28:37 -
minimalistic-core-api-for-recognizers
[r1439] minimalistic core API for recognizers
Proposal
2025-02-22 21:41:29 -
minimalistic-core-api-for-recognizers
[r1438] minimalistic core API for recognizers
Proposal
2025-02-22 10:04:11 -
minimalistic-core-api-for-recognizers
[r1437] minimalistic core API for recognizers
Proposal
2025-02-22 09:09:43 -
minimalistic-core-api-for-recognizers
[r1436] minimalistic core API for recognizers
Proposal
2025-02-20 21:39:26 -
minimalistic-core-api-for-recognizers
[r1435] minimalistic core API for recognizers
Proposal
2025-02-20 16:40:03 -
minimalistic-core-api-for-recognizers
[r1434] minimalistic core API for recognizers
Proposal
2025-02-19 21:50:22 -
minimalistic-core-api-for-recognizers
[r1433] minimalistic core API for recognizers
Proposal
2025-02-17 15:29:33 -
minimalistic-core-api-for-recognizers
[r1432] minimalistic core API for recognizers
Proposal
2025-02-17 06:45:34 -
minimalistic-core-api-for-recognizers
[r1431] minimalistic core API for recognizers
Proposal
2025-02-17 06:33:43 -
minimalistic-core-api-for-recognizers
[r1430] minimalistic core API for recognizers
Proposal
2025-02-17 01:31:51 -
minimalistic-core-api-for-recognizers
[r1429] minimalistic core API for recognizers
Proposal
2025-02-17 00:37:20 -
minimalistic-core-api-for-recognizers
[r1428] minimalistic core API for recognizers
Proposal
2025-02-16 23:03:46 -
minimalistic-core-api-for-recognizers
[r1427] minimalistic core API for recognizers
Proposal
2025-02-16 18:45:17 -
minimalistic-core-api-for-recognizers
[r1426] minimalistic core API for recognizers
Proposal
2025-02-15 09:57:48 -
minimalistic-core-api-for-recognizers
[r1425] minimalistic core API for recognizers
Proposal
2025-02-14 15:18:17 -
minimalistic-core-api-for-recognizers
[r1424] minimalistic core API for recognizers
Proposal
2025-02-14 11:21:35 -
minimalistic-core-api-for-recognizers
[r1423] minimalistic core API for recognizers
Proposal
2025-02-13 14:17:51 -
minimalistic-core-api-for-recognizers
[r1422] minimalistic core API for recognizers
Proposal
2025-02-13 13:14:50 -
tools, NAMEtoSTRING
[r1421] `NAME>STRING` result is transient
Request for clarification
2025-01-23 14:13:32 -
tools, NAMEtoSTRING
[r1420] `NAME>STRING` result is transient
Request for clarification
2025-01-23 09:57:57 -
core, ColonNONAME
[r1419] where definition is compiled?
Request for clarification
2025-01-23 08:29:12 -
tools, NAMEtoSTRING
[r1418] `NAME>STRING` result is transient
Request for clarification
2025-01-23 08:09:47 -
core, ColonNONAME
[r1417] where definition is compiled?
Request for clarification
2025-01-23 08:00:15 -
core, ERASE
[r1416]
Example
2025-01-18 03:42:19 -
core, SMDivREM
[r1415] There is error in testing
Comment
2025-01-09 12:02:44 -
core, SMDivREM
[r1414] There is error in testing
Comment
2025-01-08 19:05:30 -
tools, CODE
[r1413] May `CODE` be a parsing word?
Request for clarification
2024-12-31 10:48:46 -
minimalistic-core-api-for-recognizers
[r1412] minimalistic core API for recognizers
Proposal
2024-12-15 22:00:00 -
remove-the-rules-of-find-
[r1411] Remove the “rules of FIND”
Proposal
2024-12-10 15:17:09 -
tools, BracketDEFINED
[r1410] The case of undefined interpretation semantics
Request for clarification
2024-12-10 15:17:03 -
minimalistic-core-api-for-recognizers
[r1409] minimalistic core API for recognizers
Proposal
2024-12-09 10:00:24 -
minimalistic-core-api-for-recognizers
[r1408] minimalistic core API for recognizers
Proposal
2024-12-09 09:38:01 -
minimalistic-core-api-for-recognizers
[r1407] minimalistic core API for recognizers
Proposal
2024-12-09 07:25:04 -
core, qDO
[r1406] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-09 07:07:25 -
minimalistic-core-api-for-recognizers
[r1405] minimalistic core API for recognizers
Proposal
2024-12-08 22:59:20 -
core, qDO
[r1404] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-08 20:45:55 -
core, qDO
[r1403] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-08 19:17:59 -
core, qDO
[r1402] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-08 18:25:20 -
core, qDO
[r1401] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-08 10:46:00 -
core, qDO
[r1400] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-07 15:46:16 -
core, qDO
[r1399] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-07 08:36:05 -
core, qDO
[r1398] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-07 07:29:52 -
minimalistic-core-api-for-recognizers
[r1397] minimalistic core API for recognizers
Proposal
2024-12-07 07:22:49 -
core, qDO
[r1396] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-06 16:07:14 -
octal-prefix
[r1395] Octal prefix
Proposal
2024-12-04 17:36:50 -
known-undefined-word-xlerb
[r1394] Known undefined word XLERB
Proposal
2024-12-04 17:05:22 -
octal-prefix
[r1393] Octal prefix
Proposal
2024-12-04 14:19:10 -
octal-prefix
[r1392] Octal prefix
Proposal
2024-12-04 14:06:02 -
known-undefined-word-xlerb
[r1391] Known undefined word XLERB
Proposal
2024-12-04 11:59:41 -
minimalistic-core-api-for-recognizers
[r1390] minimalistic core API for recognizers
Proposal
2024-12-04 01:37:18 -
core, qDO
[r1389] Return Stack Notation Mildly Inaccurate
Request for clarification
2024-12-04 00:31:07 -
minimalistic-core-api-for-recognizers
[r1388] minimalistic core API for recognizers
Proposal
2024-12-02 02:30:07 -
octal-prefix
[r1387] Octal prefix
Proposal
2024-12-01 23:08:02 -
known-undefined-word-xlerb
[r1386] Known undefined word XLERB
Proposal
2024-12-01 22:31:28 -
minimalistic-core-api-for-recognizers
[r1385] minimalistic core API for recognizers
Proposal
2024-12-01 17:52:37 -
octal-prefix
[r1384] Octal prefix
Proposal
2024-12-01 16:04:13 -
octal-prefix
[r1383] Octal prefix
Proposal
2024-12-01 09:31:10 -
octal-prefix
[r1382] Octal prefix
Proposal
2024-12-01 07:48:48 -
known-undefined-word-xlerb
[r1381] Known undefined word XLERB
Proposal
2024-12-01 04:13:54 -
known-undefined-word-xlerb
[r1380] Known undefined word XLERB
Proposal
2024-12-01 02:50:44 -
octal-prefix
[r1379] Octal prefix
Proposal
2024-12-01 02:33:56 -
minimalistic-core-api-for-recognizers
[r1378] minimalistic core API for recognizers
Proposal
2024-11-29 18:18:40 -
string, SEARCH
[r1377] Possible Reference Implementation
Suggested reference implementation
2024-11-28 04:07:51 -
known-undefined-word-xlerb
[r1376] Known undefined word XLERB
Proposal
2024-11-27 20:51:54 -
known-undefined-word-xlerb
[r1375] Known undefined word XLERB
Proposal
2024-11-27 20:40:55 -
known-undefined-word-xlerb
[r1374] Known undefined word XLERB
Proposal
2024-11-27 16:30:56 -
known-undefined-word-xlerb
[r1373] Known undefined word XLERB
Proposal
2024-11-26 01:12:30 -
search, FIND
[r1372] diff from CORE FIND?
Request for clarification
2024-11-25 08:36:33 -
remove-the-rules-of-find-
[r1371] Remove the “rules of FIND”
Proposal
2024-11-23 18:46:34 -
cs-drop-revised-2019-08-22-
[r1370] CS-DROP (revised 2019-08-22)
Proposal
2024-11-20 16:49:28 -
minimalistic-core-api-for-recognizers
[r1369] minimalistic core API for recognizers
Proposal
2024-11-13 09:32:32 -
incorrect-use-of-semantics-terms
[r1368] Incorrect use of semantics terms
Proposal
2024-11-08 13:16:17 -
new-words-latest-name-and-latest-name-in
[r1367] New words: latest-name and latest-name-in
Proposal
2024-11-08 11:19:32 -
new-words-latest-name-and-latest-name-in
[r1366] New words: latest-name and latest-name-in
Proposal
2024-11-07 22:05:41 -
incorrect-use-of-semantics-terms
[r1365] Incorrect use of semantics terms
Proposal
2024-11-07 13:43:25 -
minimalistic-core-api-for-recognizers
[r1364] minimalistic core API for recognizers
Proposal
2024-11-05 03:29:18 -
minimalistic-core-api-for-recognizers
[r1363] minimalistic core API for recognizers
Proposal
2024-11-05 01:26:19 -
new-words-latest-name-and-latest-name-in
[r1362] New words: latest-name and latest-name-in
Proposal
2024-11-04 20:33:24 -
minimalistic-core-api-for-recognizers
[r1361] minimalistic core API for recognizers
Proposal
2024-11-04 11:21:24 -
core, MTimes
[r1360] Incorrect test case
Suggested Testcase
2024-11-04 04:06:09 -
minimalistic-core-api-for-recognizers
[r1359] minimalistic core API for recognizers
Proposal
2024-11-04 01:16:31 -
minimalistic-core-api-for-recognizers
[r1358] minimalistic core API for recognizers
Proposal
2024-11-02 22:37:33 -
new-words-latest-name-and-latest-name-in
[r1357] New words: latest-name and latest-name-in
Proposal
2024-11-02 21:50:25 -
new-words-latest-name-and-latest-name-in
[r1356] New words: latest-name and latest-name-in
Proposal
2024-11-02 19:39:02 -
new-words-latest-name-and-latest-name-in
[r1355] New words: latest-name and latest-name-in
Proposal
2024-11-02 18:54:41 -
new-words-latest-name-and-latest-name-in
[r1354] New words: latest-name and latest-name-in
Proposal
2024-11-02 13:18:51 -
core, TwoTimes
[r1353] Bad test case
Example
2024-11-02 07:27:39 -
minimalistic-core-api-for-recognizers
[r1352] minimalistic core API for recognizers
Proposal
2024-10-31 18:45:59 -
minimalistic-core-api-for-recognizers
[r1351] minimalistic core API for recognizers
Proposal
2024-10-08 08:43:25 -
exception
[r1350] Exception word set is not optional any more
Comment
2024-10-07 15:09:31 -
block, EMPTY-BUFFERS
[r1349] Behavior of EMPTY-BUFFERS when BLK is nonzero
Request for clarification
2024-10-07 14:49:31 -
block, EMPTY-BUFFERS
[r1348] Behavior of EMPTY-BUFFERS when BLK is nonzero
Request for clarification
2024-10-04 13:04:14 -
tools, NAMEtoINTERPRET
[r1347] How to perform the interpretation semantics for a word
Request for clarification
2024-09-27 12:51:10 -
relax-documentation-requirements-of-ambiguous-conditions
[r1346] Relax documentation requirements of Ambiguous Conditions
Proposal
2024-09-27 10:26:28 -
revised-proposal-process
[r1345] Revised Proposal Process
Proposal
2024-09-27 10:10:08 -
relax-documentation-requirements-of-ambiguous-conditions
[r1344] Relax documentation requirements of Ambiguous Conditions
Proposal
2024-09-27 10:07:57 -
relax-documentation-requirements-of-ambiguous-conditions
[r1343] Relax documentation requirements of Ambiguous Conditions
Proposal
2024-09-26 22:02:11 -
test
[r1342] Test
Proposal
2024-09-26 21:40:51 -
test
[r1341] Test
Proposal
2024-09-26 21:40:14 -
test
[r1340] Test
Proposal
2024-09-26 21:39:01 -
core-ext-s-should-reference-file-ext-s-
[r1339] Core-ext S\" should reference File-ext S\"
Proposal
2024-09-26 16:53:11 -
implementations-requiring-both-32-bit-single-floats-and-64-bit-double-floats-
[r1338] Implementations requiring BOTH 32 bit single floats and 64 bit double floats.
Proposal
2024-09-26 16:46:27 -
wlscope-wordlists-switching-made-easier
[r1337] WLSCOPE -- wordlists switching made easier
Proposal
2024-09-26 16:38:53 -
bl-rationale-is-wrong
[r1336] BL rationale is wrong
Proposal
2024-09-26 16:23:52 -
bl-rationale-is-wrong
[r1335] BL rationale is wrong
Proposal
2024-09-26 16:21:49 -
multi-tasking-proposal
[r1334] Multi-Tasking Proposal
Proposal
2024-09-26 16:03:36 -
f-r-and-fr-to-support-dynamically-scoped-floating-point-variables
[r1333] F>R and FR> to support dynamically-scoped floating point variables
Proposal
2024-09-26 15:48:45 -
minimalistic-core-api-for-recognizers
[r1332] minimalistic core API for recognizers
Proposal
2024-09-26 15:33:13 -
revise-rationale-of-buffer-
[r1331] Revise Rationale of Buffer:
Proposal
2024-09-26 15:03:53 -
revise-rationale-of-buffer-
[r1330] Revise Rationale of Buffer:
Proposal
2024-09-26 15:02:15 -
revise-rationale-of-buffer-
[r1329] Revise Rationale of Buffer:
Proposal
2024-09-26 14:52:56 -
incorrect-use-of-semantics-terms
[r1328] Incorrect use of semantics terms
Proposal
2024-09-26 14:26:31 -
cs-drop-revised-2019-08-22-
[r1327] CS-DROP (revised 2019-08-22)
Proposal
2024-09-26 14:05:54 -
cs-drop-revised-2019-08-22-
[r1326] CS-DROP (revised 2019-08-22)
Proposal
2024-09-26 14:04:20 -
minimalistic-core-api-for-recognizers
[r1325] minimalistic core API for recognizers
Proposal
2024-09-26 13:55:18 -
tools, NAMEtoINTERPRET
[r1324] How to perform the interpretation semantics for a word
Request for clarification
2024-09-26 13:37:10 -
common-terminology-for-recognizers-discurse-and-specifications
[r1323] Common terminology for recognizers discurse and specifications
Proposal
2024-09-26 13:31:54 -
tick-and-undefined-execution-semantics-2
[r1322] Tick and undefined execution semantics - 2
Proposal
2024-09-26 13:28:51 -
16-bit-memory-access
[r1321] 16-bit memory access
Proposal
2024-09-26 12:56:46 -
32-bit-memory-operators
[r1320] 32-bit memory operators
Proposal
2024-09-26 12:55:26 -
include-a-revised-79-standard-specification-for-to-core-ext-
[r1319] Include a revised 79-STANDARD Specification for "><" To "Core Ext"
Proposal
2024-09-26 12:41:54 -
test
[r1318] Test
Proposal
2024-09-26 12:40:16 -
special-memory-access-words
[r1317] Special memory access words
Proposal
2024-09-26 11:38:48 -
special-memory-access-words
[r1316] Special memory access words
Proposal
2024-09-26 10:58:00 -
support-for-single-line-comments-during-evaluate-
[r1315] Support for single line comments during `evaluate`
Proposal
2024-09-26 10:00:47 -
allow-the-text-interpreter-to-use-word-and-the-pictured-numeric-output
[r1314] Allow the text interpreter to use `WORD` and the pictured numeric output
Proposal
2024-09-26 09:30:40 -
relax-documentation-requirements-of-ambiguous-conditions
[r1313] Relax documentation requirements of Ambiguous Conditions
Proposal
2024-09-25 16:54:43 -
relax-documentation-requirements-of-ambiguous-conditions
[r1312] Relax documentation requirements of Ambiguous Conditions
Proposal
2024-09-25 16:53:09 -
tools, NAMEtoINTERPRET
[r1311] How to perform the interpretation semantics for a word
Request for clarification
2024-09-25 14:01:30 -
better-wording-for-data-field-term
[r1310] Better wording for "data field" term
Proposal
2024-09-25 13:33:10 -
tools, NAMEtoINTERPRET
[r1309] How to perform the interpretation semantics for a word
Request for clarification
2024-09-25 12:44:48 -
tools, NAMEtoINTERPRET
[r1308] How to perform the interpretation semantics for a word
Request for clarification
2024-09-24 12:42:54 -
tools, NAMEtoINTERPRET
[r1307] How to perform the interpretation semantics for a word
Request for clarification
2024-09-24 11:06:57 -
core, PICK
[r1306] Clarification on what constitutes an ambiguous condition for this word.
Request for clarification
2024-09-20 04:19:48 -
special-memory-access-words
[r1305] Special memory access words
Proposal
2024-09-19 14:36:24 -
core, WORD
[r1304] Behavior on oversized WORD
Request for clarification
2024-09-05 17:19:16 -
core, WORD
[r1303] Behavior on oversized WORD
Request for clarification
2024-09-05 16:32:34 -
core, WORD
[r1302] Behavior on oversized WORD
Request for clarification
2024-09-05 08:18:41 -
core, WORD
[r1301] Behavior on oversized WORD
Request for clarification
2024-09-04 17:01:50 -
cs-drop-revised-2019-08-22-
[r1300] CS-DROP (revised 2019-08-22)
Proposal
2024-09-03 21:43:58 -
exclude-zero-from-the-data-types-that-are-identifiers
[r1299] Exclude zero from the data types that are identifiers
Proposal
2024-08-31 17:30:15 -
block, EMPTY-BUFFERS
[r1298] Behavior of EMPTY-BUFFERS when BLK is nonzero
Request for clarification
2024-08-31 14:33:42 -
core, ABORT
[r1297] State of other stacks after ABORT
Request for clarification
2024-08-31 13:18:20 -
core, FILL
[r1296] Suggested reference implementation
Suggested reference implementation
2024-08-14 15:33:05 -
block, EMPTY-BUFFERS
[r1295] Behavior of EMPTY-BUFFERS when BLK is nonzero
Request for clarification
2024-08-13 11:04:28 -
block, EMPTY-BUFFERS
[r1294] Behavior of EMPTY-BUFFERS when BLK is nonzero
Request for clarification
2024-08-13 09:20:12 -
tools, TRAVERSE-WORDLIST
[r1293] shadowed names
Request for clarification
2024-08-12 20:23:21 -
core, ELSE
[r1292] Resolve the forward reference orig1 using the location following the appended run-time semantics.
Comment
2024-08-12 07:40:55 -
core, ELSE
[r1291] Resolve the forward reference orig1 using the location following the appended run-time semantics.
Comment
2024-08-11 14:15:21 -
core, ELSE
[r1290] Resolve the forward reference orig1 using the location following the appended run-time semantics.
Comment
2024-08-11 14:13:03 -
tools, NtoR
[r1289] Why do we use +n and not u in the stack diagram for n>r and nr>
Request for clarification
2024-08-11 11:40:02 -
core, ELSE
[r1288] Resolve the forward reference orig1 using the location following the appended run-time semantics.
Comment
2024-08-11 10:47:14 -
multi-tasking-proposal
[r1287] Better API for multitasking
Comment
2024-08-09 18:44:12 -
usage
[r1286] Temporary removing system-compilation items
Request for clarification
2024-08-09 16:06:47 -
usage
[r1285] Temporary removing system-compilation items
Request for clarification
2024-08-09 11:52:54 -
core, QUIT
[r1284] The reference implementation is incorrect
Suggested reference implementation
2024-08-09 09:46:50 -
core, ABORT
[r1283] State of other stacks after ABORT
Request for clarification
2024-08-09 06:42:38 -
usage
[r1282] Temporary removing system-compilation items
Request for clarification
2024-08-09 06:36:08 -
core, Colon
[r1281] definion and use of colon-sys and nest-sys
Request for clarification
2024-08-05 08:31:13 -
core, Colon
[r1280] definion and use of colon-sys and nest-sys
Request for clarification
2024-08-05 04:56:59 -
core, Colon
[r1279] definion and use of colon-sys and nest-sys
Request for clarification
2024-08-05 03:28:07 -
string, DivSTRING
[r1278] Unspecified ambiguous condition in /STRING
Request for clarification
2024-08-05 02:18:50 -
string, DivSTRING
[r1277] Unspecified ambiguous condition in /STRING
Request for clarification
2024-08-03 14:14:25 -
core, LITERAL
[r1276] compile semantics or compile action of literal word
Request for clarification
2024-08-02 08:55:36 -
core, LITERAL
[r1275] compile semantics or compile action of literal word
Request for clarification
2024-08-01 19:03:57 -
core, LITERAL
[r1274] compile semantics or compile action of literal word
Request for clarification
2024-08-01 15:26:41 -
core, LITERAL
[r1273] compile semantics or compile action of literal word
Request for clarification
2024-08-01 07:24:34 -
core, LITERAL
[r1272] compile semantics or compile action of literal word
Request for clarification
2024-07-31 18:23:04 -
core, LITERAL
[r1271] compile semantics or compile action of literal word
Request for clarification
2024-07-31 17:29:26 -
allow-the-text-interpreter-to-use-word-and-the-pictured-numeric-output
[r1270] Allow the text interpreter to use `WORD` and the pictured numeric output
Proposal
2024-07-31 14:42:03 -
core, LITERAL
[r1269] compile semantics or compile action of literal word
Request for clarification
2024-07-30 07:51:06 -
core, LITERAL
[r1268] compile semantics or compile action of literal word
Request for clarification
2024-07-30 07:00:43 -
core, LITERAL
[r1267] compile semantics or compile action of literal word
Request for clarification
2024-07-29 17:43:04 -
core, SAVE-INPUT
[r1266] SAVE-INPUT
Comment
2024-07-11 12:53:42 -
locals, bColon
[r1265] Stack diagram for `{:`
Request for clarification
2024-07-01 17:00:40 -
tools, NtoR
[r1264] Why do we use +n and not u in the stack diagram for n>r and nr>
Request for clarification
2024-06-30 13:53:25 -
float, REPRESENT
[r1263] Behavior of `represent` when buffer length is zero
Request for clarification
2024-06-29 16:15:09 -
float, REPRESENT
[r1262] Behavior of `represent` when buffer length is zero
Request for clarification
2024-06-29 00:00:46 -
special-memory-access-words
[r1261] Special memory access words
Proposal
2024-06-26 17:38:13 -
special-memory-access-words
[r1260] Special memory access words
Proposal
2024-06-23 17:28:45 -
special-memory-access-words
[r1259] Special memory access words
Proposal
2024-06-21 12:24:06 -
string-store-and-fetch
[r1258] String store and fetch
Proposal
2024-06-21 11:48:01
