Hi Michael,
compInst is a unique identifier a test component at run time. It is left
open to TTCN-3 RTS implementers what exactly want to choose to represent
a test component at run time but it could be something like a process id
or thread id. It does not have to be human readable. You can think of it
as the value that is stored (internally) when you assign the return of
the create operation to a component variable.
This field comes back from the time that there was no way of naming
component instances via TTCN-3 itself (and to this day it is not
required to name them). The value in this field is important to manage,
e.g., by test adapter implementers to target specific components where
to send data to.
Hope this helps,
stephan
>
Original Message
> From: active_ttcn3 : mts stf133 ttcn version 3 - active members only
> [This email address is being protected from spambots. You need JavaScript enabled to view it.] On Behalf Of Michael Sperber
> Sent: 12 January 2009 14:17
> To: TTCN3
> Subject: Question about TRI C language binding
>
> I'm looking at clause 7.2.1 of the V3.2.1 TRI spec. It says:
>
> typedef struct TriComponentId
> {
> BinaryString compInst;
> String compName;
> QualifiedName compType;
> } TriComponentId;
>
> NOTE 2: compInst is for component instance.
>
> What's a "component instance" in this context, and why is it a
> BinaryString? Where does this value come from? Further down (in the
> definition of TriPortId), the term "component instance" is used to
> refer
> to a value of type TriComponentId.
>
> (The 4.0.0 draft has exactly the same stuff.)
>
> --
> Regards,
> Mike
