search

saeaadl / emv2

AADL Error Model V2 annex language
0 stars 0 forks source link

nested subcomponent path in error condition expressions #26

Open reteprelief opened 8 years ago

reteprelief commented 8 years ago

EMV2 subclauses are not required for each level in the AADL component hierarchy. Therefore, we need to be able to identify an outgoing propagation of a subcomponent further down in outgoing propagation condition and composite error state declarations. The current syntax limits to only one.

jjhugues commented 4 years ago

Closed as this has been implemented

joeseibel commented 2 years ago

Has this been fully implemented? I'm looking at the grammar rule error_condition_trigger in section E.8:

error_condition_trigger ::=
  error_behavior_event_identifier [ error_type_set ]
  | [ in ] incoming_error_propagation_point [ error_type_set_or_noerror ]
  | subcomponent_identifier . outgoing_error_propagation_point [ error_type_set_or_noerror ]

To support nested subcomponents, it should be this:

error_condition_trigger ::=
  error_behavior_event_identifier [ error_type_set ]
  | [ in ] incoming_error_propagation_point [ error_type_set_or_noerror ]
  | { subcomponent_identifier . }+ outgoing_error_propagation_point [ error_type_set_or_noerror ]