Hi Stephan,
indeed there have been two CRs, which however have been merged - the fix will be
in TCI 3.2.1 - which then is hopefully taken by the tool vendors
- please do not go for different implementations.
Cheers, Ina.
>
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 Stephan Schulz
> Sent: Friday, October 06, 2006 9:42 AM
> To: This email address is being protected from spambots. You need JavaScript enabled to view it.
> Subject: Omit and TCI value interface
>
> And one more while I am at it ...
>
> Yet another question has been raised as to how to set fields to
>omit in codec implementations with TCI value operations.
> At ETSI we have encountered this problem as well in context of the
>WiMax test suite.
>
> The answer is that this is a bug in the TCI standard - it is
>missing an explicit "set omit" operation an at the same time the
>descirption of the newInstance operation does not explicitly state
>that optional record fields should be initialized to omit.
> I have been told and I checked this that there is 2 different CRs
>in the pipe on this issue (so 2 different solutions) - but at this
>point the maintenance STF is no longer in session... Even if it was
>in session a fix would take some time to ripple through to the
>tools :).
>
> So what to do in the meantime?
> As far as I know tools offer usually a proprietary solution for
>this problem. So either they offer their own operation or they
>initialize the value to omit during creation. Of course you should
>check with your tool vendor.
> Tool vendors please feel free to comment here :).
>
> Hope this helps,
> stephan
>
