|Re: Question regarding mapping of components and parameters [message #1831282 is a reply to message #1831279]
||Sun, 16 August 2020 13:17
| Gábor Szalai
Registered: December 2015
I tried to test it, but the map param works from function for me.|
See the small attached example. Can you try it?
You can check the generated code also.
Code generated for map without param:
TTCN_Runtime::map_port(self, CT_component_p1.get_name(), SYSTEM_COMPREF, "p2", tmp_4);
Code generated for map with param, see the set_param call:
TTCN_Runtime::map_port(self, CT_component_p1.get_name(), SYSTEM_COMPREF, CTS_component_p2.get_name(), tmp_2);
|Re: Question regarding mapping of components and parameters [message #1838676 is a reply to message #1831322]
||Wed, 03 March 2021 13:21
| Moritz Klass
Registered: August 2020
Hey all, sorry, to reopen this issue. I am now returning to this project.|
In the referenced bug ticket the two bugs are reported as closed. My ttcn_compiler version is 7.2.pl0 and the bug seems to be still there (and extended).
I am now using the parallel runtime. The TTCN code is the following:
log("Going to pass ", vc_tcp_tls_parameter);
and the generated C code is the following:
TTCN_Runtime::map_port(self, ComponentsAndPorts::SEC__Tester_component_pt__TCP__TLS__SEC__Port.get_name(), SYSTEM_COMPREF, ComponentsAndPorts::SystemSEC_component_pt__TCP__TLS__SEC__Port.get_name(), tmp_6);
I am not able to receive the parameter in the port, despite using the self (or the mtc, too) component.
[Updated on: Wed, 03 March 2021 13:23]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02766 seconds