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
From the MEF Fault Tree description (chapter 4, section 1):
If a variable or a parameter is declared more than once,
tools should emit a warning
and consider only the last definition as the good one (the previous ones are just ignored).
This is strange for a declarative modeling language
since now the order of declarations matters.
It is more like assignments of imperative languages.
As tested with XFTA,
it doesn't allow 'redefinition'.
I went this direction as well with SCRAM.
I could imagine many subtle analysis discrepancies
due to the allowance of redefinitions.
Imagine working with multi-file models.
Now if the order of files is changed or not remembered,
the analysis may be inconsistent
if it contains redefinitions spread across files.
The text was updated successfully, but these errors were encountered:
From the MEF Fault Tree description (chapter 4, section 1):
This is strange for a declarative modeling language
since now the order of declarations matters.
It is more like assignments of imperative languages.
As tested with XFTA,
it doesn't allow 'redefinition'.
I went this direction as well with SCRAM.
I could imagine many subtle analysis discrepancies
due to the allowance of redefinitions.
Imagine working with multi-file models.
Now if the order of files is changed or not remembered,
the analysis may be inconsistent
if it contains redefinitions spread across files.
The text was updated successfully, but these errors were encountered: