search

osate / ErrorModelV2

Old AADL EMV2 annex repository, kept for reference
3 stars 10 forks source link

Correct grammar for flow marked as error #67

Closed brlarson closed 10 years ago

brlarson commented 10 years ago

Consistently, the Xtext for EMV2 reports an error for flows: flows --model error in detection and reporting mame: error path monitor_mode{MonitorModeError} -> alarm_control(AlarmError);

gets error description:
mismatched input '(' expecting ';' Monitor.aadl /isolette-ksu/aadl/packages line: 12 /isolette-ksu/aadl/packages/Monitor.aadl Xtext Check (fast)

There are almost 100 such (erroneous) error reports. I presume that these error reports are related: Incoming path type constraint is not contained in type set of outgoing propagation monitor_mode Monitor.aadl /isolette-ksu/aadl/packages line: 15 /isolette-ksu/aadl/packages/Monitor.aadl Xtext Check (normal)

reteprelief commented 10 years ago

Brian,

you need to use curly brackets around the error type on the right hand side. This is a change to has occurred two meetings ago. All error types have curly brackets around them.

brlarson commented 10 years ago

Oh, you mean the one meeting I've missed in the last three years because there was a Dagstuhl seminar featuring my earlier work the same week as the committee met in Toulouse! Serves me right. I'll never miss another meeting!