You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: