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
Currently, . is used for two different actions in our specification:
Qualifying types and literals imported from another package
Accessing message fields
This makes it harder for a reader of the specification to differentiate the meaning of such a construct.
A similar question was already raised in #91, but we decided to keep the dot notation. As we are now integrating support for sessions, I would like to reconsider this decision.
Options
. / . (current syntax; similar to Ada, Python, ...)
state NETWORK_IN_CONTENT isbegin
Plaintext := GreenTLS.Content'(Data => TLS_Record_Message.Fragment);
transition
then ERROR_INTERNAL_ERROR
if Plaintext'Valid = False
then NETWORK_IN_HANDSHAKE
if TLS_Record_Message.Tag = TLS_Record.HANDSHAKE
then NETWORK_IN_ALERT
if TLS_Record_Message.Tag = TLS_Record.ALERT
then ERROR_INTERNAL_ERROR
endNETWORK_IN_CONTENT;
:: / . (similar to C++, Rust)
state NETWORK_IN_CONTENT isbegin
Plaintext := GreenTLS::Content'(Data => TLS_Record::Message.Fragment);
transition
then ERROR_INTERNAL_ERROR
if Plaintext'Valid = False
then NETWORK_IN_HANDSHAKE
if TLS_Record::Message.Tag = TLS_Record::HANDSHAKE
then NETWORK_IN_ALERT
if TLS_Record::Message.Tag = TLS_Record::ALERT
then ERROR_INTERNAL_ERROR
endNETWORK_IN_CONTENT;
\ / -> (similar to PHP)
state NETWORK_IN_CONTENT isbegin
Plaintext := GreenTLS\Content'(Data => TLS_Record\Message->Fragment);
transition
then ERROR_INTERNAL_ERROR
if Plaintext'Valid = False
then NETWORK_IN_HANDSHAKE
if TLS_Record\Message->Tag = TLS_Record\HANDSHAKE
then NETWORK_IN_ALERT
if TLS_Record\Message->Tag = TLS_Record\ALERT
then ERROR_INTERNAL_ERROR
endNETWORK_IN_CONTENT;
The text was updated successfully, but these errors were encountered:
Currently,
.
is used for two different actions in our specification:This makes it harder for a reader of the specification to differentiate the meaning of such a construct.
A similar question was already raised in #91, but we decided to keep the dot notation. As we are now integrating support for sessions, I would like to reconsider this decision.
Options
.
/.
(current syntax; similar to Ada, Python, ...)::
/.
(similar to C++, Rust)\
/->
(similar to PHP)The text was updated successfully, but these errors were encountered: