SSH login [message #1807056] |
Tue, 21 May 2019 16:33  |
Eclipse User |
|
|
|
Hi Elemer,
After cloning, the following SSH Client: https://github.com/eclipse/titan.TestPorts.SSHCLIENTasp
We came across this compiling error (Cannot determine the type of the incoming message) on these specific lines in SSHCLIENTasp_echo.ttcn and SSHCLIENTasp_functions.ttcn:
[] SSH_PCO.receive(?) -> value respFragment
[] SSH_PCO.receive(?) -> value msg
Would it come from (?) due to missing API ?
Regards - David
[Updated on: Tue, 21 May 2019 16:33] by Moderator
|
|
|
|
Re: SSH login [message #1807062 is a reply to message #1807061] |
Wed, 22 May 2019 02:18  |
Eclipse User |
|
|
|
Hi David,
Roland is right ,
in 6.5.1 we have introduced a more restrictive (and backwards incompatible) behaviour to align with the standard:
Changes implemented:
- '*' (any value or none) is no longer allowed as the matching template of 'receive', 'catch' and 'done' operations and as the return values' matching template in 'getreply' operations;
- the type of the value redirect is no longer used to determine the incoming message type (in 'receive', 'catch' and 'done' operations); the compiler must be able to determine the type from the matching template alone (if multiple message types), or an error is displayed.)
Example:
someport.receive(*) -> value var0 {} will be replaced with someport.receive(vartype:?) -> value var0 {}
(where vartype is the type of variable var0)
someport.receive(?) -> value var0 {} will be replaced with someport.receive(vartype:?) -> value var0 {}
(in case several message types can be received)
Note: someport.receive(?) -> value var0 {} remains valid if only one message type can be received (the compiler will infer the vartype)
someport.receive(*) {} will be replaced with someport.receive {}
someport.receive(?) {} will be replaced with someport.receive {}
but we did not correct all the sample codes affected.
The change suggested by Roland should fix it.
Best regards
Elemer
|
|
|
Powered by
FUDForum. Page generated in 0.03801 seconds