Contributions
These are all contributions and replies sorted latest first (Markdown version).
Contributions:
Replies:
-
an-alternative-to-the-recognizer-proposal
An alternative to the RECOGNIZER proposal
Proposal
2020-09-05 23:06:38 -
recognizer
Recognizer
Proposal
2020-09-05 21:40:18 -
an-alternative-to-the-recognizer-proposal
An alternative to the RECOGNIZER proposal
Proposal
2020-09-05 15:29:50 -
an-alternative-to-the-recognizer-proposal
An alternative to the RECOGNIZER proposal
Proposal
2020-09-05 15:23:52 -
recognizer
Recognizer
Proposal
2020-09-04 20:21:59 -
recognizer
Recognizer
Proposal
2020-09-04 17:52:36 -
nestable-recognizer-sequences
Nestable Recognizer Sequences
Proposal
2020-09-04 11:53:28 -
recognizer
Recognizer
Proposal
2020-09-03 19:37:40 -
traverse-wordlist-does-not-find-unnamed-unfinished-definitions
Traverse-wordlist does not find unnamed/unfinished definitions
Proposal
2020-09-03 17:37:15 -
reword-the-term-execution-token-
Reword the term "execution token"
Proposal
2020-09-03 17:17:39 -
reword-the-term-execution-token-
Reword the term "execution token"
Proposal
2020-09-03 17:05:44 -
tools, BracketELSE
Case-sensitivity independent implementation
Suggested reference implementation
2020-09-03 16:16:44 -
tools, BracketELSE
Reference implementation does not seem to cope with changes to the stack
Request for clarification
2020-09-03 16:13:59 -
traverse-wordlist-does-not-find-unnamed-unfinished-definitions
Traverse-wordlist does not find unnamed/unfinished definitions
Proposal
2020-09-03 15:43:48 -
licence-to-use-reference-implementations
Licence to use reference implementations
Proposal
2020-09-03 15:36:47 -
licence-to-use-reference-implementations
Licence to use reference implementations
Proposal
2020-09-03 15:30:37 -
implement
license
Request for clarification
2020-09-03 15:16:10 -
reword-the-term-execution-token-
Reword the term "execution token"
Proposal
2020-09-03 14:50:43 -
cs-drop-revised-2019-08-22-
CS-DROP (revised 2019-08-22)
Proposal
2020-09-03 13:58:50 -
core, SMDivREM
There is error in testing
Comment
2020-09-03 13:29:53 -
nestable-recognizer-sequences
Nestable Recognizer Sequences
Proposal
2020-09-03 13:06:12 -
cs-drop-revised-2019-08-22-
CS-DROP (revised 2019-08-22)
Proposal
2020-09-03 12:26:48 -
xml-forth-standard-migration-from-latex-to-docbook
XML Forth Standard - migration from LaTeX to DocBook
Proposal
2020-09-03 11:43:41 -
cs-drop-revised-2019-08-22-
CS-DROP (revised 2019-08-22)
Proposal
2020-09-03 11:43:10 -
cs-drop-revised-2019-08-22-
CS-DROP (revised 2019-08-22)
Proposal
2020-09-03 11:20:11 -
wording-declare-undefined-interpretation-semantics-for-locals
Wording: declare undefined interpretation semantics for locals
Proposal
2020-09-03 10:04:21 -
call-for-vote-ambiguous-condition-in-16-3-3
Call for Vote - Ambiguous condition in 16.3.3
Proposal
2020-09-03 08:53:24 -
core, StoD
Word set of S>D word
Request for clarification
2020-09-02 21:10:07 -
core, WITHIN
sample implementation that can also be interpreted
Suggested reference implementation
2020-09-02 15:31:15 -
core, RECURSE
Why RECURSE is needed?
Request for clarification
2020-09-02 15:28:08 -
remove-the-rules-of-find-
Remove the “rules of FIND”
Proposal
2020-09-02 13:55:59 -
nestable-recognizer-sequences
Nestable Recognizer Sequences
Proposal
2020-09-02 13:10:42 -
call-for-vote-ambiguous-condition-in-16-3-3
Call for Vote - Ambiguous condition in 16.3.3
Proposal
2020-09-02 12:19:35 -
traverse-wordlist-does-not-find-unnamed-unfinished-definitions
Traverse-wordlist does not find unnamed/unfinished definitions
Proposal
2020-09-02 12:15:59 -
traverse-wordlist-does-not-find-unnamed-unfinished-definitions
Traverse-wordlist does not find unnamed/unfinished definitions
Proposal
2020-09-02 11:56:44 -
call-for-vote-ambiguous-condition-in-16-3-3
Call for Vote - Ambiguous condition in 16.3.3
Proposal
2020-09-02 11:17:55 -
remove-the-rules-of-find-
Remove the “rules of FIND”
Proposal
2020-09-02 09:40:34 -
traverse-wordlist-does-not-find-unnamed-unfinished-definitions
Traverse-wordlist does not find unnamed/unfinished definitions
Proposal
2020-09-02 07:44:20 -
remove-the-rules-of-find-
Remove the “rules of FIND”
Proposal
2020-09-02 07:24:19 -
xml-forth-standard-migration-from-latex-to-docbook
XML Forth Standard - migration from LaTeX to DocBook
Proposal
2020-09-02 05:59:27 -
remove-the-rules-of-find-
Remove the “rules of FIND”
Proposal
2020-09-01 19:34:59 -
tools, TRAVERSE-WORDLIST
Unfindable definitions
Comment
2020-09-01 17:43:40 -
vocabulary
VOCABULARY
Proposal
2020-09-01 16:17:01 -
remove-the-rules-of-find-
Remove the “rules of FIND”
Proposal
2020-09-01 15:31:12 -
multi-tasking-proposal
Multi-Tasking Proposal
Proposal
2020-09-01 14:18:46 -
core, Colon
The parts of execution semantics and the calling definition
Request for clarification
2020-08-31 15:40:53 -
core, Colon
The parts of execution semantics and the calling definition
Request for clarification
2020-08-31 05:24:29 -
wording-declare-undefined-interpretation-semantics-for-locals
Wording: declare undefined interpretation semantics for locals
Proposal
2020-08-30 15:10:27 -
wording-declare-undefined-interpretation-semantics-for-locals
Wording: declare undefined interpretation semantics for locals
Proposal
2020-08-30 13:19:41 -
tools
Getting execution semantics from nt
Request for clarification
2020-08-30 12:20:32 -
tools
Getting execution semantics from nt
Request for clarification
2020-08-30 10:53:29 -
wording-declare-undefined-interpretation-semantics-for-locals
Wording: declare undefined interpretation semantics for locals
Proposal
2020-08-30 10:04:46 -
wording-declare-undefined-interpretation-semantics-for-locals
Wording: declare undefined interpretation semantics for locals
Proposal
2020-08-30 09:01:01 -
same-name-token-for-different-words
Same name token for different words
Proposal
2020-08-29 20:55:48 -
tools
Getting execution semantics from nt
Request for clarification
2020-08-29 16:46:36 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-29 16:09:53 -
recognizer
Recognizer
Proposal
2020-08-29 12:28:14 -
same-name-token-for-different-words
Same name token for different words
Proposal
2020-08-29 11:22:50 -
search
Get execution semantics from nt
Request for clarification
2020-08-29 08:14:47 -
same-name-token-for-different-words
Same name token for different words
Proposal
2020-08-28 15:12:13 -
nestable-recognizer-sequences
Nestable Recognizer Sequences
Proposal
2020-08-28 13:08:28 -
recognizer
Recognizer
Proposal
2020-08-28 12:29:27 -
clarify-find-more-classic-approach
Clarify FIND, more classic approach
Proposal
2020-08-28 08:00:31 -
case-insensitivity
Case insensitivity
Proposal
2020-08-27 18:50:37 -
locals
Recognizer for locals
Comment
2020-08-27 17:15:57 -
locals
Recognizer for locals
Comment
2020-08-27 11:09:16 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-26 23:57:01 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-26 16:36:31 -
find-name
find-name
Proposal
2020-08-26 14:41:54 -
locals
Recognizer for locals
Comment
2020-08-25 09:01:33 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-24 23:42:43 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-24 23:38:37 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-24 23:36:24 -
2020-forth-standards-meeting-agenda
2020 Forth Standards meeting agenda
Proposal
2020-08-23 20:23:12 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-23 14:52:06 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-23 13:05:06 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-22 20:46:52 -
nestable-recognizer-sequences
Nestable Recognizer Sequences
Proposal
2020-08-22 17:16:05 -
recognizer
Recognizer
Proposal
2020-08-22 17:10:31 -
rationale
Annex A section and paragraph numbering has gone wrong
Request for clarification
2020-08-22 16:18:31 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-22 14:34:37 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-22 13:49:20 -
optional-ieee-754-binary-floating-point-word-set
OPTIONAL IEEE 754 BINARY FLOATING-POINT WORD SET
Proposal
2020-08-22 06:53:23 -
find-name
find-name
Proposal
2020-08-22 06:12:45 -
core, BL
ASCII version of BL
Suggested reference implementation
2020-08-21 17:08:53 -
core, BL
ASCII version of BL
Suggested reference implementation
2020-08-19 07:10:46 -
find-name
find-name
Proposal
2020-08-16 16:20:59 -
core, BL
An example
Example
2020-08-15 17:10:48 -
find-name
find-name
Proposal
2020-08-15 09:54:18 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-13 18:38:31 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-13 13:22:05 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-12 12:30:50 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-12 12:27:26 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-12 09:27:46 -
2020-forth-standards-meeting-agenda
2020 Forth Standards meeting agenda
Proposal
2020-08-12 08:33:49 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-11 12:30:40 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-11 06:29:33 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-10 18:22:48 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-03 12:46:07 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-03 10:59:07 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-03 10:47:15 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-02 17:23:54 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-01 21:00:10 -
core, PARSE
What happens when parse reaches the end of the parse area and the parse delimiter was not found?
Request for clarification
2020-08-01 20:27:42 -
tools, SYNONYM
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-30 13:10:12 -
tools, SYNONYM
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-29 21:37:30 -
tools, SYNONYM
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-27 14:00:18 -
tools, SYNONYM
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-27 09:29:43 -
recognizer
Recognizer
Proposal
2020-07-20 20:39:45 -
tools, BracketELSE
Case-sensitivity independent implementation
Suggested reference implementation
2020-07-03 08:35:50 -
Overhaul 2020: Proposals
Comment
2020-06-24 21:41:41 -
same-name-token-for-different-words
Same name token for different words
Proposal
2020-06-24 21:27:49 -
searching-for-right-bracket-doesn-t-return-
Searching for ] (right-bracket) doesn't return ]
Proposal
2020-06-23 15:16:44 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-06-23 10:02:04 -
core, SMDivREM
There is error in testing
Comment
2020-06-22 16:56:58 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-06-11 12:24:07 -
f-r-and-fr-to-support-dynamically-scoped-floating-point-variables
F>R and FR> to support dynamically-scoped floating point variables
Proposal
2020-06-11 07:00:33 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-06-10 12:29:04 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-06-09 16:59:51 -
core, PlusLOOP
Numeric overflow/underflow
Request for clarification
2020-06-08 09:49:29 -
core, PlusLOOP
Numeric overflow/underflow
Request for clarification
2020-06-08 09:41:43 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-06-02 13:08:01 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-06-02 04:23:49 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-06-02 03:31:49 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-05-30 12:11:07 -
core, StoD
Word set of S>D word
Request for clarification
2020-05-30 09:36:27 -
core, StoD
Word set of S>D word
Request for clarification
2020-05-30 04:18:38 -
core, StoD
Word set of S>D word
Request for clarification
2020-05-30 04:18:16 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-05-28 08:14:52 -
tools, BracketELSE
Reference implementation does not seem to cope with changes to the stack
Request for clarification
2020-04-11 10:20:02 -
core, FILL
Suggested reference implementation
Suggested reference implementation
2020-04-04 15:40:24 -
wording-declare-undefined-interpretation-semantics-for-locals
Wording: declare undefined interpretation semantics for locals
Proposal
2020-03-08 16:31:47 -
wording-declare-undefined-interpretation-semantics-for-locals
Wording: declare undefined interpretation semantics for locals
Proposal
2020-03-08 16:20:37 -
clarify-find-more-classic-approach
Clarify FIND, more classic approach
Proposal
2020-03-08 14:07:18 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-03-05 16:56:05 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-03-01 17:02:35 -
recognizer-rfd-rephrase-2020
Recognizer RfD rephrase 2020
Proposal
2020-03-01 12:55:28 -
name-interpret-wording
NAME>INTERPRET wording
Proposal
2020-02-20 11:22:59 -
core, RECURSE
Why RECURSE is needed?
Request for clarification
2020-02-07 15:05:02 -
core, WITHIN
sample implementation that can also be interpreted
Suggested reference implementation
2020-02-07 07:26:29 -
better-wording-for-colon
Better wording for Colon
Proposal
2020-02-06 02:36:20 -
input-values-other-than-true-and-false
Input values other than true and false
Proposal
2020-01-18 17:44:21 -
input-values-other-than-true-and-false
Input values other than true and false
Proposal
2020-01-12 15:14:48 -
input-values-other-than-true-and-false
Input values other than true and false
Proposal
2020-01-12 11:50:40 -
input-values-other-than-true-and-false
Input values other than true and false
Proposal
2020-01-12 05:42:11 -
input-values-other-than-true-and-false
Input values other than true and false
Proposal
2020-01-12 01:35:57 -
input-values-other-than-true-and-false
Input values other than true and false
Proposal
2020-01-11 23:33:50 -
input-values-other-than-true-and-false
Input values other than true and false
Proposal
2020-01-11 17:44:35 -
core, RECURSE
Why RECURSE is needed?
Request for clarification
2020-01-11 10:35:06 -
core, RECURSE
Why RECURSE is needed?
Request for clarification
2020-01-11 01:25:34 -
core, RECURSE
Why RECURSE is needed?
Request for clarification
2020-01-10 09:49:12 -
core, POSTPONE
Ambiguous condition could be removed
Comment
2019-11-07 00:11:50 -
implement
license
Request for clarification
2019-10-30 11:17:45 -
case-sensitivity
Case sensitivity
Proposal
2019-10-08 09:49:20 -
tools, SYNONYM
Test cases for SYNONYM
Suggested Testcase
2019-10-03 12:09:02 -
tools, SYNONYM
Reference implementation of SYNONYM
Suggested reference implementation
2019-10-03 11:33:36 -
right-justified-text-output
Right-justified text output
Proposal
2019-09-24 13:26:38 -
core, COMPILEComma
Interpretation semantics
Comment
2019-09-19 01:38:22 -
find-name
find-name
Proposal
2019-09-16 01:34:00 -
core, IMMEDIATE
Ambiguous conditions
Comment
2019-09-14 13:24:51 -
core, Tick
Ambiguous condition in case of undefined execution semantics
Comment
2019-09-13 07:46:12 -
core, IMMEDIATE
Ambiguous conditions
Comment
2019-09-12 15:19:24 -
block, LOAD
Getting the block contents
Request for clarification
2019-09-12 15:14:42 -
core, Tick
Ambiguous condition in case of undefined execution semantics
Comment
2019-09-12 14:17:48 -
tools, BracketIF
POSTPONE [IF]
Request for clarification
2019-09-12 14:15:22 -
core, QUIT
The reference implementation is incorrect
Suggested reference implementation
2019-09-12 12:33:37 -
core, QUIT
The reference implementation is incorrect
Suggested reference implementation
2019-09-12 12:30:06 -
remove-the-rules-of-find-
Remove the “rules of FIND”
Proposal
2019-09-12 10:28:25 -
core
GNU C RESTRICT would make sense in the standard
Suggested reference implementation
2019-09-12 09:39:57 -
core, POSTPONE
Ambiguous condition could be removed
Comment
2019-09-12 08:43:39 -
tools, BracketELSE
[ELSE] without preceding [IF]
Comment
2019-09-11 17:01:16 -
case-insensitivity
Case insensitivity
Proposal
2019-09-11 16:47:28 -
tools
description of "nt" in the standard
Request for clarification
2019-09-11 00:40:05 -
clarify-find
Clarify FIND
Proposal
2019-09-10 12:44:39 -
case-insensitivity
Case insensitivity
Proposal
2019-09-10 11:18:38 -
case-insensitivity
Case insensitivity
Proposal
2019-09-10 11:07:51 -
case-sensitivity
Case sensitivity
Proposal
2019-09-10 10:28:39 -
core, POSTPONE
Ambiguous condition could be removed
Comment
2019-09-08 08:04:49 -
core, POSTPONE
Ambiguous condition could be removed
Comment
2019-09-07 16:23:36 -
core, IMMEDIATE
Ambiguous conditions
Comment
2019-09-06 16:25:33 -
tools
description of "nt" in the standard
Request for clarification
2019-09-06 14:16:58 -
clarify-find
Clarify FIND
Proposal
2019-09-06 13:40:58 -
tools
description of "nt" in the standard
Request for clarification
2019-09-06 12:17:51 -
find-name
find-name
Proposal
2019-09-06 11:56:34 -
find-name
find-name
Proposal
2019-09-06 10:55:30 -
tools
description of "nt" in the standard
Request for clarification
2019-09-06 10:40:38 -
tools
description of "nt" in the standard
Request for clarification
2019-09-06 09:45:53 -
cs-drop-revised-2019-08-22-
CS-DROP (revised 2019-08-22)
Proposal
2019-09-06 08:54:22 -
core, IMMEDIATE
Ambiguous conditions
Comment
2019-09-06 08:34:47 -
file, REFILL
Ambiguous conditions
Request for clarification
2019-09-06 08:26:50 -
cs-drop-revised-2018-08-20-
CS-DROP (revised 2018-08-20)
Proposal
2019-09-06 08:25:21 -
tools
description of "nt" in the standard
Request for clarification
2019-09-06 08:05:25 -
tools
description of "nt" in the standard
Request for clarification
2019-09-05 12:18:25 -
tighten-the-specification-of-synonym-version-1-
Tighten the specification of SYNONYM (version 1)
Proposal
2019-09-05 10:53:04 -
tighten-the-specification-of-synonym-version-1-
Tighten the specification of SYNONYM (version 1)
Proposal
2019-09-04 15:07:43 -
find-name
find-name
Proposal
2019-09-04 12:23:36 -
tools
description of "nt" in the standard
Request for clarification
2019-09-04 11:08:16 -
clarify-find
Clarify FIND
Proposal
2019-08-29 09:09:15 -
clarify-find
Clarify FIND
Proposal
2019-08-29 08:47:12 -
find-name
find-name
Proposal
2019-08-28 15:45:04 -
core, toIN
Etymology of ">IN" name
Request for clarification
2019-08-27 02:49:28 -
Search box
Comment
2019-08-25 20:12:13 -
block, LIST
Does LIST transfer data to any buffer?
Request for clarification
2019-08-13 05:46:52 -
core, toIN
Environment dependence of test cases
Request for clarification
2019-08-12 22:14:55 -
block, LIST
Does LIST transfer data to any buffer?
Request for clarification
2019-08-12 17:54:14 -
block, LIST
Does LIST transfer data to any buffer?
Request for clarification
2019-08-12 11:02:50 -
block, LOAD
Getting the block contents
Request for clarification
2019-08-12 08:10:03 -
block, LIST
Does LIST transfer data to any buffer?
Request for clarification
2019-08-12 08:06:28 -
block, LOAD
Getting the block contents
Request for clarification
2019-08-11 16:38:49 -
block, LOAD
Getting the block contents
Request for clarification
2019-08-11 16:31:06 -
block, LOAD
Getting the block contents
Request for clarification
2019-08-10 13:36:24 -
block, EVALUATE
When to set BLK to zero?
Request for clarification
2019-08-10 13:29:57 -
block, LOAD
Getting the block contents
Request for clarification
2019-08-10 11:49:44 -
core, toIN
Environment dependence of test cases
Request for clarification
2019-08-10 03:41:50 -
Session timer and preseving contributions
Example
2019-08-10 00:45:10 -
core, EVALUATE
SOURCE-ID and nesting EVALUATE
Request for clarification
2019-08-07 17:30:01 -
core
GNU C RESTRICT would make sense in the standard
Suggested reference implementation
2019-08-07 16:56:50 -
core
GNU C RESTRICT would make sense in the standard
Suggested reference implementation
2019-08-06 09:28:24 -
core, BL
Test example numeric base?
Request for clarification
2019-08-05 15:55:56 -
core, BL
Test example numeric base?
Request for clarification
2019-08-05 07:13:43 -
right-justified-text-output
Right-justified text output
Proposal
2019-08-02 11:41:11 -
right-justified-text-output
Right-justified text output
Proposal
2019-08-02 06:19:29 -
searching-for-right-bracket-doesn-t-return-
Searching for ] (right-bracket) doesn't return ]
Proposal
2019-08-01 16:08:31 -
core, BL
ASCII version of BL
Suggested reference implementation
2019-08-01 00:17:17 -
core, POSTPONE
Ambiguous condition could be removed
Comment
2019-07-20 12:50:00 -
core, POSTPONE
Ambiguous condition could be removed
Comment
2019-07-20 11:13:26 -
core, POSTPONE
Ambiguous condition could be removed
Comment
2019-07-20 08:58:14 -
exception, CATCH
The specification of CATCH
Request for clarification
2019-07-20 07:09:07 -
core, Tick
Ambiguous condition in case of undefined execution semantics
Comment
2019-07-19 15:15:22 -
core, Tick
Ambiguous condition in case of undefined execution semantics
Comment
2019-07-18 16:30:50 -
core, Tick
Ambiguous condition in case of undefined execution semantics
Comment
2019-07-16 17:07:09 -
core, TO
Ambiguous conditions
Request for clarification
2019-07-15 17:36:51 -
core, TO
Ambiguous conditions
Request for clarification
2019-07-15 10:33:53 -
tools, BracketIF
POSTPONE [IF]
Request for clarification
2019-07-11 07:55:34 -
tools, BracketIF
POSTPONE [IF]
Request for clarification
2019-07-11 07:39:47 -
tools, BracketIF
POSTPONE [IF]
Request for clarification
2019-07-11 06:33:13 -
tools, BracketIF
POSTPONE [IF]
Request for clarification
2019-07-10 19:06:17 -
core, PARSE-NAME
Etymology and naming convention issue
Comment
2019-07-10 14:33:51 -
core, BUFFERColon
the confusing names
Request for clarification
2019-07-10 07:54:38 -
core, BUFFERColon
Address between runs
Request for clarification
2019-07-10 07:50:02 -
core, PARSE-NAME
Etymology and naming convention issue
Comment
2019-07-10 07:39:57 -
core, BUFFERColon
the confusing names
Request for clarification
2019-07-10 07:29:39 -
core, BUFFERColon
Address between runs
Request for clarification
2019-07-10 07:22:06 -
bl-rationale-is-wrong
BL rationale is wrong
Proposal
2019-07-09 15:56:23 -
core, BUFFERColon
the confusing names
Request for clarification
2019-07-09 14:40:02 -
revise-rationale-of-buffer-
Revise Rationale of Buffer:
Proposal
2019-07-06 15:49:22 -
tools, BracketDEFINED
The case of undefined interpretation semantics
Request for clarification
2019-07-06 06:22:51 -
tools, BracketDEFINED
The case of undefined interpretation semantics
Request for clarification
2019-07-05 15:03:21 -
notation
What is a standard program
Comment
2019-07-05 12:47:36 -
tools, NAMEtoINTERPRET
How can the zero result be used in a Standard program?
Request for clarification
2019-07-05 10:33:38
