Notes taken by M. Anton Ertl
Accept Krishna for vote? Vote #5 7Y:0N:0A
Sergey Baranov is no longer a committee member
Covid consequences
Electronic meetings
Accepted the following amendment to the constitution (Vote #8, 12Y:0:0)
Delete the “with the exception of the Annual General Meeting” restriction from section 5.7 of the Constitution so it reads as follows:
“5.7. General Meetings may be virtual (e.g.,via Telephone, eMail, chat, etc.).”
Brexit consequences
none
Payment for services/licences
No change
Other
Vote of officers in 2020
Due to lack of secret voting: Delay until 2021 unless somebody objects
Chair
forth-standard.org works
Editor
Last public version: 2018-1
Get the document in XML with Peter Knaggs’ document type
Technical
Provide Moderator button on “Manage users”. Action: GW
Usenet postings for forth-standard.org postings: Only proposals. Undecided whether automated or in person.
Mailing lists: Yahoo no longer archives the mailing lists Move the mailing list to Forth-Gesellschaft. Action: BP PK
Treasurer
No income, no expenses, balance: 0
Recognisers
Stay as experimental proposal?
Separate POSTPONE action?
Impact of dot parser on POSTPONE?
Multi-tasking from APH
There is common practice
Implementation on GitHub
Formal proposal upcoming (memory model missing). Action: AH
Ambiguous condition and IMMEDIATE
TC answer by Bernd, 2019-09-12 15:19:24
Move from RUV, any further action?
Answer the latest reply. Action: AE
Propose to remove the ambiguous condition (from 16.3.3) that RUV points out Vote #9: 6Y:4N:2A, i.e., not accepted (no consensus reached).
no committee response
CS-DROP from UH
say orig and dest must be same size
Go to vote?
Approved by the committee. Vote #18 11Y:0N:1A
Case insensitivity
ASCII case insensitivity only.
Go to vote?
Go to CfV when forth-standard.org supports it. Action: AE
Remove the “rules of FIND” (BP)
Locals word set?
Go to vote?
Wording change proposal was accepted: Vote #10, 10Y:0:0
Reference implementation of SYNONYM (AE, RUV)
Broken reference implementation.
New reference implementation.
Vote #6:
Delete reference implementation for SYNONYM and replace with this rationale text (from original implementation):
“The implementation of SYNONYM requires detailed knowledge of the host implementation, which is why it is standardized.”
12Y:0:0 Accepted
VOCABULARY (UH)
The committee felt there was no question that this is common practice, so it skipped the CfV part and went directly to committee vote.
Vote #7:
Adopt the latest (2020-09-01) version of the VOCABULARY proposal to the standard.
12Y:0:0 Accepted
Unfindable definitions (RUV)
Wording change for TRAVERSE-WORDLIST to address the issue
Vote #20: 11Y:0:0 Accepted
Case sensitivity in [IF] and friends
Reference implementation looks good. Vote #11 to accept this reference implementation: 10Y:0:0 Accepted.
Clarify FIND and Clarify FIND, more classic approach
No action, look at it again next year.
FIND-NAME
Accepted in 2018
License (JK, RUV)
Addressed in License to use reference implementations
Vote #19: 12Y:0:0 Accepted
String, REPLACES (RUV)
Error if macro does not exist during compilation?
Proposed wording change in REPLACES:
This breaks the contiguity of the current region and is not allowed during compilation of a colon definition
with
Therefore REPLACES cannot be performed during compilation of a colon definition or in the middle of a contiguous region.
Vote #14: 11Y:0N:1A Accepted
Why RECURSE is needed (BI)
Pick a TC answer.
Request answered
Input values other than true and false [IF]
Pick flag as z/nz, vote, TC response
Vote #16 12Y:0:0 Accepted
sample implementation that can also be interpreted (MAX)
Adopt RUV’s response as TC answer.
ruv’s response is correct
Better wording for Colon (RUV)
Instead of the proposed wording, the committee accepted the following wording change (Vote #13: 11Y:0N:1A):
Replace the first paragraph of 6.1.0450 : (colon)
Skip leading space delimiters. Parse name delimited by a space. Create a definition for name, called a “colon definition”. Enter compilation state and start the current definition, producing colon-sys. Append the initiation semantics given below to the current definition.
with the following
Skip leading space delimiters. Parse name delimited by a space. Create a definition for name. Enter compilation state and start the current definition, producing colon-sys. Append the initiation semantics given below to the current definition.
NAME>INTERPRET wording (RUV)
To address the execution token issue, Proposal: Reword the term “execution token” was drafted. This is now up for review by the general public.
The parts of execution semantics and the calling definition (RUV)
Write a proposal eliminating initiation semantics of : and maybe other words. Action: AE
Recognizer RfD rephrase 2020 (UH)
Move to recogniser workshop
Discussed, see point 1.
“(” typo in a testcase (RUV)
Assign to editor
Editor fixes it. Action: PK
Wording: declare undefined interpretation semantics for locals (RUV)
Remove ambiguous conditions
The committee accepted the following wording change (Vote #17, 12Y:0:0)
This is true for (LOCAL) so we should add:
local Interpretation:
Interpretation semantics for this word are undefined.LOCALS| refers to (LOCAL) so (LOCAL) covers the case.
For {: we need to add:
name Interpretation
The interpretation semantics of name are undefinedthen remove the ambiguous condition in name Execution.
Word set of S>D word (RUV)
Leave as is?
Same name token for different words (RUV)
No committee response for now
Recognizer for locals (RUV)
No committe response
There is error in testing SM/REM (MB)
Pass to editor
Pass to editor. Action: PK
Defer Implementation (Tolich)
Recogniser (BP)
Move to recogniser workshop.
Move to workshop
Does wording imply that if you SYNONYM a word with the same name (JN)
No committee response
What happens when parse reaches the end of the parse area? (JN)
Response. Action: AE
TEST instead of TEAT in F.1 para 2 (JN)
Pass to editor
Pass to editor. Action: PK
Workshops are topics for discussion outside the formal meeting.
Future Document Format
Peter Knaggs may step down as editor. Gerald Wodni (technical director, responsible for forth-standard.org) strongly prefers staying with LaTeX. The XML format looks interesting; conversion cost, including tool conversion cost may be an issue, but there are some ideas on how to deal with it.
Stack comments
stack comments should be parseable
Stack naming S: D: F: N: R:
stack effect notation
stack effect conventions
This workshop did not happen.
Test suites
Philosophy
J Hayes sequencing
G Jackson suite
Connect with G Jackson. Action: PK
Licensing
Resulted in License to use reference implementations
Vote #19: 12Y:0:0 Accepted
CfV
Short workshop working out how CfVs should work on forth-standard.org
Recognizers
Some bikeshedding about names and terminology.
Remove the opacity of rectype to allow to perform rectype dispatch with STATE @ CELLS + @ EXECUTE. This works better with the A/B POSTPONE, if you do a POSTPONE mode (]] … [[).
Dealing with C/D POSTPONE in cross-compiling is possible (Bernd Paysan knows how to do it).
Workshop reports
See sections above
See above
Voting on officers moved to 2021
quotations wording
offline
Reference implementation does not seem to cope with changes to the stack
Had been withdrawn
Review votes
Close votes at the end of EuroForth
September 8-10, 2021 in Rome
or
September 7-9, 2021, online