Proposal: 2020 Forth Standards meeting agenda
This page is dedicated to discussing this specific proposal
ContributeContributions
StephenPelc
[146] 2020 Forth Standards meeting agendaProposal2020-08-11 21:39:27
2020 Forth Standards Meeting
1-3 Sept 2020, Online
We expect to be using BigBlueButton or Zoom or Webex or some such. If you want to rant or rave about online meeting tools, it's outside the scope of this document. For reasonable discussion, contact Stephen Pelc, stephen@mpeforth.com
Schedule
The standards meeting will be Monday-Thursday from 2:30 pm to 6:30 pm CEST with a short bio-break at 4:30. An alternative would be to do Tuesday to Thursday and Sunday afternoon. The latter solution fits with at least one committee member who doesn't do Mondays!
Participants
Review of Procedures
- Covid consequences
- Brexit consequences
- Payment for services/licences
Reports
- Chair
- Editor
- Technical
- Treasurer
Review of Proposals and Activities
- Recognisers
Stay as experimental proposal?
Separate POSTPONE action?
Impact of dot parser on POSTPONE?
Multi-tasking from APH
Ambiguous condition and IMMEDIATE
TC answer by Bernd, 2019-09-12 15:19:24
Move from RUV, any further action?
- CS-DROP from UH
say orig and dest must be same size
Go to vote?
- Case insensitivity
ASCII case insensitivity only.
Go to vote?
- Remove the “rules of FIND” (BP)
Locals word set?
Go to vote?
- Reference implementation of SYNONYM (AE, RUV)
Broken reference implementation.
New reference implementation.
VOCABULARY (UH)
Unfindable definitions (RUV)
Case sensitivity in [IF] and friends.
FIND
FIND-NAME
License (JK, RUV)
String, EPLACES (RUV)
Error if macro does not exist during compilation?
Why RECURSE is needed (BI) Pick a TC answer.
Input values other than true and false [IF]
Pick flag as z/nz, vote, TC response
- sample implementation that can also be interpreted (MAX)
Adopt RUV's response as TC answer.
Better wording for Colon (RUV)
NAME>INTERPRET wording (RUV)
The parts of execution semantics and the calling definition (RUV)
Recognizer RfD rephrase 2020 (UH)
Move to recogniser workshop
- "(" typo in a testcase (RUV)
Assign to editor
- Wording: declare undefined interpretation semantics for locals (RUV)
Remove ambiguous conditions
Word set of S>D word (RUV) Leave as is?
Same name token for different words (RUV)
Recognizer for locals (RUV)
There is error in testing SM/REM (MB)
Pass to editor
Defer Implementation (Tolich)
Recogniser (BP)
Move to recogniser workshop.
Does wording imply that if you SYNONYM a word with the same name (JN)
What happens when parse reaches the end of the parse area? (JN)
TEST instead of TEAT in F.1 para 2 (JN)
Pass to editor
Workshop Topics
Workshops are topics for discussion outside the formal meeting.
Future Document Format
Stack comments
stack comments should be parseable
Stack naming S: D: F: N: R:
stack effect notation
stack effect conventions
- Test suites
Philosophy
J Hayes sequencing
G Jackson suite
- Workshop reports
Consideration of proposals + CfV votes
Matters arising
Any other business
Date of next meeting
AntonErtl
September 1-3 is Tuesday-Thursday; elsewhere it says Monday to Thursday. Please make the dates and the days agree.
StephenPelcNew Version: 2020 Forth Standards meeting agenda
2020 Forth Standards Meeting
1-3 Sept 2020, Online
We expect to be using BigBlueButton or Zoom or Webex or some such. If you want to rant or rave about online meeting tools, it's outside the scope of this document. For reasonable discussion, contact Stephen Pelc, stephen@mpeforth.com
Schedule
The standards meeting will be Monday-Thursday from 2:30 pm to 6:30 pm CEST with a short bio-break at 4:30. An alternative would be to do Tuesday to Thursday and Sunday afternoon. The latter solution
The standards meeting will be Tuesday-Thursday from 2:30 pm to 6:30 pm CEST with a short bio-break at 4:30. This solution
fits with at least one committee member who doesn't do Mondays!
Participants
Review of Procedures
- Covid consequences
- Brexit consequences
- Payment for services/licences
Reports
- Chair
- Editor
- Technical
- Treasurer
Review of Proposals and Activities
- Recognisers
Stay as experimental proposal?
Separate POSTPONE action?
Impact of dot parser on POSTPONE?
Multi-tasking from APH
Ambiguous condition and IMMEDIATE
TC answer by Bernd, 2019-09-12 15:19:24
Move from RUV, any further action?
- CS-DROP from UH
say orig and dest must be same size
Go to vote?
- Case insensitivity
ASCII case insensitivity only.
Go to vote?
- Remove the “rules of FIND” (BP)
Locals word set?
Go to vote?
- Reference implementation of SYNONYM (AE, RUV)
Broken reference implementation.
New reference implementation.
VOCABULARY (UH)
Unfindable definitions (RUV)
Case sensitivity in [IF] and friends.
FIND
FIND-NAME
License (JK, RUV)
String, EPLACES (RUV)
Error if macro does not exist during compilation?
Why RECURSE is needed (BI) Pick a TC answer.
Input values other than true and false [IF]
Pick flag as z/nz, vote, TC response
- sample implementation that can also be interpreted (MAX)
Adopt RUV's response as TC answer.
Better wording for Colon (RUV)
NAME>INTERPRET wording (RUV)
The parts of execution semantics and the calling definition (RUV)
Recognizer RfD rephrase 2020 (UH)
Move to recogniser workshop
- "(" typo in a testcase (RUV)
Assign to editor
- Wording: declare undefined interpretation semantics for locals (RUV)
Remove ambiguous conditions
Word set of S>D word (RUV) Leave as is?
Same name token for different words (RUV)
Recognizer for locals (RUV)
There is error in testing SM/REM (MB)
Pass to editor
Defer Implementation (Tolich)
Recogniser (BP)
Move to recogniser workshop.
Does wording imply that if you SYNONYM a word with the same name (JN)
What happens when parse reaches the end of the parse area? (JN)
TEST instead of TEAT in F.1 para 2 (JN)
Pass to editor
Workshop Topics
Workshops are topics for discussion outside the formal meeting.
Future Document Format
Stack comments
stack comments should be parseable
Stack naming S: D: F: N: R:
stack effect notation
stack effect conventions
- Test suites
Philosophy
J Hayes sequencing
G Jackson suite
- Workshop reports
Consideration of proposals + CfV votes
Matters arising
Any other business
Date of next meeting
PeterKnaggs
Draft minutes are now available on GitHub