Difference: UnicodeCNV_BINStmt (8 vs. 9)

Revision 92011-05-02 - JeanNeron

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

CNV BIN Statement

Line: 42 to 42
 
  1. CNV BIN from negative literal does not generate compile time error, generates 'Invalid Sign' runtime error. Might not be actual bug, just different implementation? Confirmed 4/2/11, designed this way
  2. National fields are not transcoded to their proper character set. I can CNV BIN a character from the Unicode character set (but that does not exist in the National character set as specified on the SYSPARM file) into a National field, and it will display the Unicode character. Instead, it should transcode the Unicode character to the National character, and display that.
  3. Overflow errors are not occurring at the expected limit. The max value for a 4 byte unsigned number is 4294967295, if I use this value I get overflow errors. If I decrease that by 1 to 4294967294, I do not get an overflow.
Added:
>
>
  1. Uses wrong character set? Example, I use CNV BIN to put 0xA4 into TEMP 1. This is a spiky ball character, but the debugger shows that TEMP 1 contains a Euro symbol.
  -- JeanNeron - 2011-03-11 \ No newline at end of file
 
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