Hi,
yes, the standard could be clearer in this regard.
Anyway, here is the deal:
Behaviour (function, altstep) that 'runs on' component type A may be
invoked/activated on a component of type B when B declares the same
component members (ports, consts, timer, variables) of the same types,
names, and initial values as A.
Also, in that case, a component reference of type B can be assigned to a
variable of type A.
The upcoming version of the standard includes an extension mechanism for
component types that makes exploiting this 'runs on' compatibility to
write re-usable behaviour a little bit more convenient to use.
I hope this help!
BR
Stephan
On Mon, 2005-01-17 at 14:56, ext Scott Moseley wrote:
> Dear All,
>
>
>
> Can someone point me to the thread that best discusses defines
> Components that are of Compatible Type? For some reason, I have
> missed a lot of the TTCN-3 list discussions in the past 5 months. Are
> there some examples of components that are type compatible? I find
> the TTCN-3 base spec a little obscure in this area.
>
>
>
> Thanks much,
>
> Scott
>
>
