-
Notifications
You must be signed in to change notification settings - Fork 6
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
Allow with-clause without then-clause to define field length #343
Labels
specification
Related to specification package (e.g., specification parsing)
Projects
Comments
treiher
added
the
specification
Related to specification package (e.g., specification parsing)
label
Jul 16, 2020
treiher
added a commit
that referenced
this issue
Oct 14, 2020
treiher
added a commit
that referenced
this issue
Oct 14, 2020
treiher
added a commit
that referenced
this issue
Oct 19, 2020
treiher
added a commit
that referenced
this issue
Oct 19, 2020
treiher
added a commit
that referenced
this issue
Oct 19, 2020
treiher
added a commit
that referenced
this issue
Oct 19, 2020
treiher
added a commit
that referenced
this issue
Oct 19, 2020
treiher
added a commit
that referenced
this issue
Oct 19, 2020
treiher
added a commit
that referenced
this issue
Oct 19, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Being able to directly define the field length at the specific field could simplify the specification in cases, where the length of the field does not depend on any condition, but multiple paths exist (i.e. multiple incoming edges contain the same length aspect). Such a length specification should be internally translated into length aspects at all incoming edges. No incoming edge should be allowed to have a length aspect in such a case. In #95 we already thought about introducing a similar feature for conditions.
Examples
TLS
Verify_Data : Opaque with Length => Message'Length;
Instead of:
IPv4
Instead of:
The text was updated successfully, but these errors were encountered: