Digest #162 2021-09-02
#F orth Standard Committee Meeting Draft agenda
7-9 Sept 2021 15:00-19:30 UTC
Online - see chat.forth-standard.org,
Agenda Draft 1 - 1 Sept 2021
Review of Procedures
- Covid consequences
- Brexit consequences
- Payment for services and licences Until now, this has always been done informally.
- Closure mechanism for discussions to avoid inconsequential stuff being discussed at the next meeting.
- Real name of user should be required by the web site, but need not be displayed. A standard is a public document.
Election of officers
- Chair - Nominations needed
- Editor - Peter Knaggs
- Technical - Gerald Wodni
- Treasurer - Bernd Paysan
Review of Proposals
Interpretation semantic for locals are undefined (SFP)
According to AE, see vote 17, 12Y:0:0 of the 2020 meeting.
Reword the term "execution token" (AE)
Chair's comment. Go back to the beginning and get your ducks in a row. You have to work together. There are plenty of systems with recognisers now. Please see what common practice is. Standards are not the place for flashy new design.
Common terminology for recognizers discurse and specifications (RUV)
minimalistic core API for recognizers (BP)
An alternative to the RECOGNIZER proposal (APH)
Tick and undefined execution semantics (RUV)
EMIT and non-ASCII values (AE)
Reference implementations are not normative (AE)
COMPILE, wording (RUV)
Adopt Gerry Jackson Test suite (SFP)
PLACE and +PLACE or APPEND (UHO)
Review of Discussions
Is TICK immediate?
Run-Time Section is Missing Words (JP)
Conversion error LaTex to HTML? (Editor)
Size of implementation dependent data types (RUV)
ALLOT in ROMmable systems (TG9541)
(Almost) portable implemetation of
XC-WIDTH return value - -1 for unknown.
D>S Inaccurate Test Case - close?
Implementation for «S"» via the immediacy mechanism (RUV)
Portable implementation for SYNONYM (RUV)
Suggested reference implementation
###T est suite, WHILE DEPTH
[ is IMMEDIATE
Workshops are topics for discussion outside the formal meeting.
###Future Document Format
###S tack comments stack comments should be parseable Stack naming S: D: F: N: R: stack effect notation stack effect conventions
Consideration of proposals + CfV votes
Any other business
Date of next meeting
I support this proposal, but much prefer
"It is not an error to tick a word. There may be an error if the returned result is used incorrectly." "I understand this point. But an ambiguous condition is a formal thing."
The ambiguous condition is generated by using the result, not by ticking the word.
I systems wish to perform checks in ' and friends, that is their privilege. However, the standard should never force a system to do so.
I seen nothing that indicates that such sizes need to be consistent. However, you need to be sure that you have covered all use cases and have included the relevant version data (size) in the returned data.