Difference: UnicodeCALLStmt (1 vs. 2)

Line: 1 to 1

META TOPICPARENT	name="UnicodeTestPlan"

Changed:

<
<

CALL

>
>

Changed:

<
<

Expected Behaviour

>
>

The initial implementation of Unicode will not allow passed arguments to be UNICODE Alpha fields or NATIONAL Alpha fields. A runtime error should occur if a UNICODE Alpha value argument is passed to a CALL statement.
This decision will break any applications which happen to use a TEMP field to pass arguments to a CALL statement.

Added:

>
>

Do non UNICODE or NATIONAL arguments still work correctly?

Are proper errors thrown when passing UNICODE or NATIONAL fields to a CALL operation?

Does the CALL statement itself allow for UNICODE or NATIONAL fields to define the call function name?

Does not appear to test for Unicode or National fields, so it allows them to be passed. Tested by passing TEMP 80 to RT_SLCT_AP.

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="UnicodeTestPlan"

Expected Behaviour

The initial implementation of Unicode will not allow passed arguments to be UNICODE Alpha fields or NATIONAL Alpha fields. A runtime error should occur if a UNICODE Alpha value argument is passed to a CALL statement.
This decision will break any applications which happen to use a TEMP field to pass arguments to a CALL statement.

Does not appear to test for Unicode or National fields, so it allows them to be passed. Tested by passing TEMP 80 to RT_SLCT_AP.

-- JeanNeron - 2011-03-09