Difference: UnicodeRECEIVE_LOCALStmt (5 vs. 6)

Line: 1 to 1

META TOPICPARENT	name="UnicodeTestPlan"

RECEIVE / LOCAL Statements

Line: 19 to 19

Test all encoding to see if they act as a RESTORE (DEFAULT VALUE). * They do not, but they don't under previous versions either *

Changed:

<
<

Assign a value like 10. to --- X, and PASS that into a subroutine (shared). RECEIVE it as a National or Unicode field type, and append a one to the string, then exit. After the subroutine returns, --- X will contain 101.000000000000. Note all the trailing zeros, this doesn't happen under 5.0.3, or if you use a Raw type field. If you PASS --- X again into a National or Unicode field, it will receive all the trailing zeroes and the string will contain 101.000000000000 instead of just 101.
Transcode errors are reported as 'Overflow Error' at run time. Should probably use the 'Transcode Error' message so the designer has a better idea of the problem. Example: Pass Raw field to a subroutine (shared), receive as Unicode or National, then append a non Raw character to it & return. Runtime error occurs after the return.
Same as above, but on a RECEIVE. Example, pass a Unicode field containing a unicode value, receive a RAW, runtime error is 'Overflow error', probably s/b 'Transcode Error'
Same as 2), but on a RECEIVE with National fields. Example, pass a National field containing a national value, receive a RAW, runtime error is 'Overflow error', probably s/b 'Transcode Error'

>
>

Assign a value like 10. to --- X, and PASS that into a subroutine (shared). RECEIVE it as a National or Unicode field type, and append a one to the string, then exit. After the subroutine returns, --- X will contain 101.000000000000. Note all the trailing zeros, this doesn't happen under 5.0.3, or if you use a Raw type field. If you PASS --- X again into a National or Unicode field, it will receive all the trailing zeroes and the string will contain 101.000000000000 instead of just 101. * FIXED* July 4 engine
Transcode errors are reported as 'Overflow Error' at run time. Should probably use the 'Transcode Error' message so the designer has a better idea of the problem. Example: Pass Raw field to a subroutine (shared), receive as Unicode or National, then append a non Raw character to it & return. Runtime error occurs after the return. * FIXED* July 4 engine
Same as above, but on a RECEIVE. Example, pass a Unicode field containing a unicode value, receive a RAW, runtime error is 'Overflow error', probably s/b 'Transcode Error' * FIXED* July 4 engine
Same as 2), but on a RECEIVE with National fields. Example, pass a National field containing a national value, receive a RAW, runtime error is 'Overflow error', probably s/b 'Transcode Error' * FIXED* July 4 engine

Does not report transcode errors when a non national character is passed into a national field (ie, pass unicode, receive national). ** Not a bug FAD**

Deleted:

<
<

-- PeteBrower - 2011-03-17 \ No newline at end of file