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

Unexpected order dependencies #167

Open
dburgener opened this issue Apr 12, 2023 · 0 comments
Open

Unexpected order dependencies #167

dburgener opened this issue Apr 12, 2023 · 0 comments

Comments

@dburgener
Copy link
Owner

Generally speaking policy should not be order dependent. In the current implementation, let bindings, module definitions and system definitions may be order dependent. If they are split across multiple files, the order they are processed in is compiler defined, which makes this problem worse.

Cascade should preprocess the definitions to know what bindings and definitions are defined before processing their definitions to remove this dependency.

dburgener added a commit to dburgener/refpolicy3 that referenced this issue Apr 12, 2023
Let bindings and module definitions should not be order dependent.  Due
to a current libcascade bug that is expected to be carried into 0.1,
they are order dependent.  Reorder to make current libcascade happy, and
revert this after the bug is fixed.

dburgener/cascade#167
dburgener added a commit to dburgener/refpolicy3 that referenced this issue Apr 12, 2023
Let bindings and module definitions should not be order dependent.  Due
to a current libcascade bug that is expected to be carried into 0.1,
they are order dependent.  Reorder to make current libcascade happy, and
revert this after the bug is fixed.

dburgener/cascade#167
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant