Hi Michael,
> I'm trying to understand the intention behind the C language binding
> for
> TriTimerId, defined to be BinaryString:
>
> - Is the data of a BinaryString that represents a timer intended to
> convey any specific information? (The specs for the Java binding
say
> a little bit more, but are still vague on issues such as the naming
> of
> timers that are in arrays.) If it's supposed to be something like
> the
> name of the variable in the TTCN-3 program, why is it a BinaryString
> and not a "regular" string?
[STS] A binary string has been chosen as it leaves more implementation
freedom for run time system implementers. These strings are "generated"
or assigned in the TE and passed into the PA and each string value
corresponds to exactly one timer. A character string may be one way of
implementing the standard.
Note that there are explicit as well as implicit timers, e.g., a timer
guarding a test case or procedure based call ... so assigning a
meaningful name is not always as easy as it looks.
> - What determines the identity of a timer? The address passed to the
> various triTimerXXX functions, or the binary string? I.e., if I
have
[STS] I am not sure what you mean .. the answer is the timerId parameter
in the various functions which should be of type binary string.
> two different objects that have the same bits in their BinaryString
> representation, do they represent the same timer or different
timers?
> (I'm assuming different timers, but am not sure.)
[STS] No it is the same timer. Think of it as a character string (which
is one valid way of representing a timer identifier. The same string
refers to the same timer.
BTW - there is no objects in the C .. so your statement about different
objects is a bit confusing.
Salut,
stephan
>
> Any help is much appreciated!
>
> --
> Regards,
> Mike