Hi all,

We have just been looking at the TCI-CD interface and noted that there = seems
to be no operation defined to set optional fields to omit.
Neither is there any mention that new value instances should have their =
optional fields be initialized to the omit value.
I have been told that codec implementers rely on using tool proprietary =
interfaces or value initilization schemes to get feilds to be omitted

My questions are:
Am I overlooking something? Has this operation intentionally been = omitted from
the TCI-CD API?
(note that there is a getter/checker function for omit defined .. but = not
setter)

Is if anybody is aware of any submitted CRs towards this issue? If so = what is
its state?

Thanks,
Stephan Schulz

I'm a bit puzzled by how getTypeForName gets used. The 3.2.1 TCI
document has an example in 11.1.2 ("Requesting module parameters") which
says:

"At first, the type of a module parameter is requested, then the value
can be constructed by the TM and given to the TE."

How does TM know the type (or type name) of the module parameter?
AFAICS, tciGetModulePar effectively passes only the name of the module
parameter, not its type. (And tciGetModuleParameters doesn't provide
the types either, right?)

Any help would be much appreciated!

--
Regards,
Mike

Hello Mike,

tciGetModuleParameters passes for each module parameter the parameter
name and the default value. If there is a default value, then the type
can be retrieved from value.

If there is no default value, the information has to be provided
externally. E.g. by a file containing a list of module parameter names
and types.

Best regards

Thomas


>

---

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 ext
>Michael Sperber
>Sent: Tuesday, 23. December 2008 10:50
>To: This email address is being protected from spambots. You need JavaScript enabled to view it.
>Subject: TCI question
>
>I'm a bit puzzled by how getTypeForName gets used. The 3.2.1 TCI
>document has an example in 11.1.2 ("Requesting module
>parameters") which
>says:
>
>"At first, the type of a module parameter is requested, then the value
>can be constructed by the TM and given to the TE."
>
>How does TM know the type (or type name) of the module parameter?
>AFAICS, tciGetModulePar effectively passes only the name of the module
>parameter, not its type. (And tciGetModuleParameters doesn't provide
>the types either, right?)
>
>Any help would be much appreciated!
>
>--
>Regards,
>Mike
>