Port type definition, collision of types
Summary
Titan does not differentiate between types in port definition if type and parent type are listed too
Steps and/or TTCN-3 code to reproduce
type integer integeralias (1..10);
type port mypt message{
inout integer, integeralias;
}with{extension "internal";}
What is the current bug behavior?
This code yields an error, as integer is provided twice in the inout list of the port type.
What is the expected correct behavior?
integer and integeralias (which can be an alias or a value restricted subtype of integer) should be considered two types
Relevant logs and/or screenshots
../src/control_flow.ttcn:3.1-5.1: In type definition `mypt':
../src/control_flow.ttcn:4.3-29: In `inout' list:
../src/control_flow.ttcn:4.18-29: error: Duplicate incoming message type `integer'
../src/control_flow.ttcn:4.9-15: note: Type `integer' is already listed here
Possible fixes
Titan version
8.1.0
Platform details (OS type and version)
Microsoft Windows 10 Enterprise 10.0.19042
/cc @aknappqwt @mmagyari