The CALL command starts an operation call in animation or tracing. TestConductor can use this command to launch operations.
[Object name]->CALL([operation call]
[, signature (optional)])
operation call
If the operation is static, this is the class name. Otherwise, it is the name of the object that performs the call. The format is as follows:
[method name]([list of argument values])
signature
Specifies the signature of the operation. This optional argument is used to distinguish between overloaded functions. For example:
a->CALL(f(5, "Hello"),f(int,char*))
A[0]->CALL(f(5))
Invokes f(5) on the object A[0]
A->CALL(g("Hello, World!"))
Invokes g(char*) on the object A
The following table lists sample notifications.
| Action | Message Format |
|---|---|
| The operation will be called when the application resumes. | Message: <CALL command> sent. For example: Message: Utility->CALL(sq(2)) sent. |
| The operation returned, and there is a return value. | <CALL command> returned <return
value> For example: Utility->CALL(sq2)) returned 1.41421. |
| No matching operation is found. | Unable to perform <CALL command>,
no matching operation found. For example: Unable to perform a->CALL(f()), no matching operation found. |
| More than one matching operation is found. | Unable to perform <CALL command>,
more than a single matching operation found. For example: Unable to perform a->CALL(f(5)), more than a single matching operation found. This can happen only if you use the command-line interface and do not specify the signature. If you use the window, this message will never be displayed because the window always enters the signature. |