Eclipse Community Forums: Eclipse Titan » Issue with ETSI LibCommon

Help

Home

Home » Eclipse Projects » Eclipse Titan » Issue with ETSI LibCommon(TITAN - TTCN-3 variant - ETSI LibCommon)

Show: Today's Messages :: Show Polls :: Message Navigator

Issue with ETSI LibCommon [message #1771442]

Fri, 25 August 2017 06:20

Yann Garcia

Messages: 145
Registered: June 2016

Senior Member

Dear All,

I just build a new version of TITAN based on the github repositiry and I got a strange issue while building the ETSI LibCommon.
For instance, in the module LibCommon_DataStrings.ttcn, I got the error
../ttcn/LibCommon_DataStrings.ttcn:29:5: note: In type definition `Bit1':
../ttcn/LibCommon_DataStrings.ttcn:29:43: error: No encoding rules defined for type `bitstring'

The Bit1 is declared as:
type bitstring Bit1 length(1) with {variant "FIELDLENGTH(1)" }; //with {encode "length(1)"};

Do you have any hit to fix it?

Many thanks in advance for your support,

Yann

[Updated on: Fri, 25 August 2017 06:21]

Report message to a moderator

Re: Issue with ETSI LibCommon [message #1771458 is a reply to message #1771442]

Fri, 25 August 2017 09:19

Gyorgy Rethy

Messages: 31
Registered: April 2015

Member

Hi Yann,
It compiles with the release /6 R2A for me, so I think this behaviour shall be related to the ongoing implementation of the new standard feature of multiple encoding of a type.
In earlier Titan versions, if Titan recognized by the syntax that a variant attribute belongs to a given encoding, assigned this encoding to the type implicitly. This will not work with multiple encodings, the encode specification shall be explicit.
I cannot ask our developer right now what is the current status, but I propose to add
with { encode "RAW"}
after the closing bracket of the module.

Just a hint: Titan RAW codec, if no FIELDLENGTH is attached to a fix-length restricted type, will use the type's length restriction. So, it should be enough simply comment out "with {encode "length(1)"};" :-)

Report message to a moderator