Skip to content
This repository was archived by the owner on Oct 3, 2024. It is now read-only.

Fail to parse the annex content when not using types #26

Closed
juli1 opened this issue Jul 2, 2013 · 1 comment
Closed

Fail to parse the annex content when not using types #26

juli1 opened this issue Jul 2, 2013 · 1 comment

Comments

@juli1
Copy link
Contributor

juli1 commented Jul 2, 2013

Hello,

In the following, the component PositionSensor must parse. Are the types mandatory now ?

package Device_pkgs
public
with EMV2, ErrorLibrary, ErrorLibrary;

device d1
features
pin: in data port;
pout: out data port;

annex EMV2{**
use types ErrorLibrary;
error propagations
pout: out propagation {ServiceOmission};
flows
es1: error source pout;
end propagations;

};
end d1;
device PositionSensor
features
PositionReading: out data port;
Annex EMV2 {

error propagations
PositionReading: out propagation;
flows
ef1: error source PositionReading;
end propagations;

**};

end PositionSensor;

end Device_pkgs;

@reteprelief
Copy link
Contributor

Fixed. It is optional but the parser required the type set.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants