Proposal: 2020 Forth Standards meeting agenda

Informal

This page is dedicated to discussing this specific proposal

ContributeContributions

StephenPelcavatar of StephenPelc 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

  1. Covid consequences
  2. Brexit consequences
  3. Payment for services/licences

Reports

  1. Chair
  2. Editor
  3. Technical
  4. Treasurer

Review of Proposals and Activities

  1. Recognisers
    Stay as experimental proposal?
    Separate POSTPONE action?
    Impact of dot parser on POSTPONE?

  2. Multi-tasking from APH

  3. Ambiguous condition and IMMEDIATE
    TC answer by Bernd, 2019-09-12 15:19:24
    Move from RUV, any further action?

  4. CS-DROP from UH
    say orig and dest must be same size
    Go to vote?

  5. Case insensitivity
    ASCII case insensitivity only.
    Go to vote?

  6. Remove the “rules of FIND” (BP)
    Locals word set?
    Go to vote?

  7. Reference implementation of SYNONYM (AE, RUV)
    Broken reference implementation.
    New reference implementation.

  8. VOCABULARY (UH)

  9. Unfindable definitions (RUV)

  10. Case sensitivity in [IF] and friends.

  11. FIND

  12. FIND-NAME

  13. License (JK, RUV)

  14. String, EPLACES (RUV)
    Error if macro does not exist during compilation?

  15. Why RECURSE is needed (BI) Pick a TC answer.

  16. Input values other than true and false [IF]
    Pick flag as z/nz, vote, TC response

  17. sample implementation that can also be interpreted (MAX)
    Adopt RUV's response as TC answer.

  18. Better wording for Colon (RUV)

  19. NAME>INTERPRET wording (RUV)

  20. The parts of execution semantics and the calling definition (RUV)

  21. Recognizer RfD rephrase 2020 (UH)
    Move to recogniser workshop

  22. "(" typo in a testcase (RUV)
    Assign to editor

  23. Wording: declare undefined interpretation semantics for locals (RUV)
    Remove ambiguous conditions

  24. Word set of S>D word (RUV) Leave as is?

  25. Same name token for different words (RUV)

  26. Recognizer for locals (RUV)

  27. There is error in testing SM/REM (MB)
    Pass to editor

  28. Defer Implementation (Tolich)

  29. Recogniser (BP)
    Move to recogniser workshop.

  30. Does wording imply that if you SYNONYM a word with the same name (JN)

  31. What happens when parse reaches the end of the parse area? (JN)

  32. TEST instead of TEAT in F.1 para 2 (JN)
    Pass to editor

Workshop Topics

Workshops are topics for discussion outside the formal meeting.

  1. Future Document Format

  2. Stack comments
    stack comments should be parseable
    Stack naming S: D: F: N: R:
    stack effect notation
    stack effect conventions

  3. Test suites
    Philosophy
    J Hayes sequencing
    G Jackson suite

  4. Workshop reports

Consideration of proposals + CfV votes

Matters arising

Any other business

Date of next meeting

AntonErtlavatar of AntonErtl

September 1-3 is Tuesday-Thursday; elsewhere it says Monday to Thursday. Please make the dates and the days agree.

StephenPelcavatar of StephenPelcNew Version

Hide differences

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

  1. Covid consequences
  2. Brexit consequences
  3. Payment for services/licences

Reports

  1. Chair
  2. Editor
  3. Technical
  4. Treasurer

Review of Proposals and Activities

  1. Recognisers
    Stay as experimental proposal?
    Separate POSTPONE action?
    Impact of dot parser on POSTPONE?

  2. Multi-tasking from APH

  3. Ambiguous condition and IMMEDIATE
    TC answer by Bernd, 2019-09-12 15:19:24
    Move from RUV, any further action?

  4. CS-DROP from UH
    say orig and dest must be same size
    Go to vote?

  5. Case insensitivity
    ASCII case insensitivity only.
    Go to vote?

  6. Remove the “rules of FIND” (BP)
    Locals word set?
    Go to vote?

  7. Reference implementation of SYNONYM (AE, RUV)
    Broken reference implementation.
    New reference implementation.

  8. VOCABULARY (UH)

  9. Unfindable definitions (RUV)

  10. Case sensitivity in [IF] and friends.

  11. FIND

  12. FIND-NAME

  13. License (JK, RUV)

  14. String, EPLACES (RUV)
    Error if macro does not exist during compilation?

  15. Why RECURSE is needed (BI) Pick a TC answer.

  16. Input values other than true and false [IF]
    Pick flag as z/nz, vote, TC response

  17. sample implementation that can also be interpreted (MAX)
    Adopt RUV's response as TC answer.

  18. Better wording for Colon (RUV)

  19. NAME>INTERPRET wording (RUV)

  20. The parts of execution semantics and the calling definition (RUV)

  21. Recognizer RfD rephrase 2020 (UH)
    Move to recogniser workshop

  22. "(" typo in a testcase (RUV)
    Assign to editor

  23. Wording: declare undefined interpretation semantics for locals (RUV)
    Remove ambiguous conditions

  24. Word set of S>D word (RUV) Leave as is?

  25. Same name token for different words (RUV)

  26. Recognizer for locals (RUV)

  27. There is error in testing SM/REM (MB)
    Pass to editor

  28. Defer Implementation (Tolich)

  29. Recogniser (BP)
    Move to recogniser workshop.

  30. Does wording imply that if you SYNONYM a word with the same name (JN)

  31. What happens when parse reaches the end of the parse area? (JN)

  32. TEST instead of TEAT in F.1 para 2 (JN)
    Pass to editor

Workshop Topics

Workshops are topics for discussion outside the formal meeting.

  1. Future Document Format

  2. Stack comments
    stack comments should be parseable
    Stack naming S: D: F: N: R:
    stack effect notation
    stack effect conventions

  3. Test suites
    Philosophy
    J Hayes sequencing
    G Jackson suite

  4. Workshop reports

Consideration of proposals + CfV votes

Matters arising

Any other business

Date of next meeting

PeterKnaggsavatar of PeterKnaggs

Draft minutes are now available on GitHub

Reply New Version