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.

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

ENFORCE-statement does not combine with a MEANING statement #1522

Open
RieksJ opened this issue Oct 29, 2024 · 1 comment
Open

ENFORCE-statement does not combine with a MEANING statement #1522

RieksJ opened this issue Oct 29, 2024 · 1 comment
Labels
bug Indicates an unexpected problem or unintended behavior component: compiler component:parser Syntax

Comments

@RieksJ
Copy link
Contributor

RieksJ commented Oct 29, 2024

The ENFORCE statement specifies a rule/constraint, as well as a working instruction to resolve violations.

Contrary to RULE statements, the ENFORCE statement does not allow a MEANING to be specified.
Since we want to provide users the ability to generate complete documentation, the ENFORCE statement should be allowed to have an associated MEANING.

@RieksJ RieksJ added bug Indicates an unexpected problem or unintended behavior component:parser Syntax component: compiler labels Oct 29, 2024
@hanjoosten
Copy link
Member

I think this is a totally valid request.

That said, this isn't easy to implement. An ENFORCE statement is currently implemented as syntactical sugar. It is translated into one or two RULEs (depending on the operator that is used). In case of := as operator, there will be two rules. The other operators will lead to a single rule. I suggest that the MEANING, will be copied to all derived rules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior component: compiler component:parser Syntax
Projects
None yet
Development

No branches or pull requests

2 participants