Generated functions -- parameter types
Summary
It might be worth thinking about the parameter types of nonexistent, generated functions
Steps and/or TTCN-3 code to reproduce
Create a restricted type (or an alias -- worth trying both cases), and call an undefined function in your TTCN-3 code with an actual parameter value (undefined("myvalue") or undefined(525)) matching this restricted type or alias. Then accept TITAN's offer to create the skeleton of this undefined function. Then try the same, but this time, instead of using a literal as an actual parameter value, use indentifiers of a variable/constant/module parameter/template value. This variable/constant/module parameter/template value shall be of the restricted type or alias. (Example: undefined(v_myvar), where v_myvar is a variable)
What is the current bug behavior?
Not sure, what is worth investigating is which formal parameter type to generate the function with in both cases: The parent type, or the closest restricted type? Maybe it's worth to give multiple offers for function signatures? (This latter would make the number of possibilities exponential as a function of the number of function parameters).
What is the expected correct behavior?
?
Relevant logs and/or screenshots
Possible fixes
Titan version
The newest one from the demo in 20220222
Platform details (OS type and version)
/cc @aknappqwt