Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement consequences of making the Exception word set mandatory #1

Open
5 tasks
ruv opened this issue Aug 20, 2022 · 0 comments
Open
5 tasks

Implement consequences of making the Exception word set mandatory #1

ruv opened this issue Aug 20, 2022 · 0 comments
Labels
inconsistency Something is inconsistent with something else

Comments

@ruv
Copy link
Collaborator

ruv commented Aug 20, 2022 •
edited
Loading

See also a comment (On the 2017 standard meeting the Exception word set was made mandatory to make it possible to remove some ambiguous conditions.).

To do:

  • Remove CORE ABORT, update EXCEPTION ABORT
  • Remove CORE ABORT", update EXCEPTION ABORT"
  • Rewrite THROW to not mention CORE ABORT
  • Update QUIT to eliminate a conflict with THROW — usually QUIT empties the exception stack too.
  • Update INCLUDE-FILE, clarify weather fileid shall be closed if an exception occurs during interpretation.
@ruv ruv mentioned this issue Sep 8, 2022
Open
25 tasks
@ruv ruv added the inconsistency Something is inconsistent with something else label Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
inconsistency Something is inconsistent with something else
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ruv