Subprogram implementations in call sequences

[Etienne13]

Dear all,

I was trying to reference a subprogram implementation in a subprogram call sequence but noticed that osate complained about it. When looking in the standard, I don't see the syntactic error I would make. I thus assume it is a bug, and put hereafter a simple example to reproduce the situation:

package call_spg_impl public

thread T end T;

subprogram S end S;

subprogram implementation S.impl end S.impl;

thread implementation T.impl calls callSeq_Default: { call_1: subprogram S.impl;}; end T.impl;

end call_spg_impl;

Best, Etienne.

[juli1]

Dear Etienne,

Can you elaborate the issue ? I do not see any bug with the latest version of OSATE. Please note that a bug relative to this issue was solved recently (see https://github.com/osate/osate2-core/issues/153). Can you try with the latest build (see. http://www.aadl.info/aadl/osate/testing/products/) or tell us how to reproduce the problem ?

Thanks again,

[Etienne13]

Sure, I probably used an old version of osate in this test; I will let you know if the problem persists or not with a newer version (but if you don't reproduce it on the small example the issue is on my side).

Etienne.

[Etienne13]

I onfirm the problem came from my version of osate, switching to the newest release fixes the problem. Sorry for the disturbance,

Etienne.

[reteprelief]

When the subprogram implementation reference is to a classifier in another package, it finds the type, but not the implementation.

[reteprelief]

fixed