contradicting string patterns only detected when creating data element
Summary
If there is a sub-subtype the string pattern of which contradicts that of its parent type (which is a subtype of charstring), this is not detected on type definition level, only when attempting to define a data element with the given type
Steps and/or TTCN-3 code to reproduce
Create module with the following contents:
type charstring MyString (pattern "abc*xyz");
type MyString MyString3 (pattern "d*xyz"); //error
testcase patterns_charstrings() runs on ct_empty{
var MyString3 v5 := "daxyz";
}
What is the current bug behavior?
Without the var MyString3 v5 := "daxyz"; line, TITAN runs the code and no error verdict is generated.
What is the expected correct behavior?
Without the var MyString3 v5 := "daxyz"; line, TITAN should be able to detect that the pattern of MyString3 contradicts the pattern of parent type MyString, and generate a compile time error.
Relevant logs and/or screenshots
Possible fixes
Titan version
8.1.0
Platform details (OS type and version)
Microsoft Windows 10 Enterprise 10.0.19042
/cc @aknappqwt