search

saeaadl / aadlv2.2

SAE AADL core language, version 2.2
1 stars 0 forks source link

Clarify requirements and permissions for subprogram classifiers in call sequences #6

Closed stevevestal closed 3 years ago

stevevestal commented 7 years ago

See an OSATE issue filed for a discussion and example,

https://github.com/osate/osate2-core/issues/796

reteprelief commented 7 years ago

Steve proposes that we remove the ability to declare subprogram calls with reference to a subprogram classifier, not a provided/required classifier or library.

reteprelief commented 7 years ago

Peter thinks we may just add a note that it is ambiguous or it has a default interpretation of one instance in a process. Jerome will look at the code generation annex to see how they interpret it there.

reteprelief commented 7 years ago

Jerome: Should we consider removing subprogram call sequences for V3?

reteprelief commented 7 years ago

Agreed to go with the editorial comment approach (two comments earlier).

reteprelief commented 7 years ago

Add the following text to "Processing Requirements and Permissions" section of 5.2: "When users specify calls in a call sequence with a reference to a classifier then the subprogram instance to be called is not specified as part of the model but left as choice to the implementer. This may be a subprogram implementation in a library that may or may not be shared." => This is 5.2 (24) in a different form