Difference: UnicodeCALLStmt (1 vs. 4)

Revision 42011-04-06 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"

CALL Statement

Line: 7 to 7
 
  • 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:
>
>
After further review, it was decided that no checking will be done by the CALL statement, therefore there are no changes to CALL for unicode.
 

Test Plan

Do non UNICODE or NATIONAL arguments still work correctly?

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

BUGS

Changed:
<
<
  1. 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.
>
>
  1. 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 \ No newline at end of file

Revision 32011-04-01 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"

CALL Statement

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

BUGS

Changed:
<
<
  1. 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.
>
>
  1. 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

Revision 22011-03-17 - PeteBrower

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"
Changed:
<
<

CALL

>
>

CALL Statement

 
Changed:
<
<
Expected Behaviour
>
>

Overview

 
  • 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:
>
>

Test Plan

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?

 

BUGS

  1. 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.

Revision 12011-03-09 - JeanNeron

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="UnicodeTestPlan"

CALL

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.

BUGS

  1. 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

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback