Difference: UnicodeSET_TEMPStmt (3 vs. 4)

Revision 42011-04-28 - JeanNeron

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

SET TEMP Statement

Line: 37 to 37
 
    • The process compiler should report this error.
    • This may break some existing applications.

Test Plan

Deleted:
<
<

ILF Editor: (untested)

 
Changed:
<
<		Test Requirements:

Does the ILF Editor allow all valid combinates from the above list?

Does the ILF Editor give a meaningful error when entering invalid combinations?

Test Results and Notes:

Untested

Process Compiler: (untested)

Test Requirements:

Does the Process Compiler allow all valid combinates from the above list?

Does the Process Compiler give a meaningful error when encountering invalid combinations? (can use Opt-88 to force saving or errors)

Test Results and Notes:

Untested

Bugs

  1. SET TEMP into a Raw Alpha does not appear to set any characters. * FIXED * March 28 engine

>
>
  1. Test SET TEMP with group fields, should produce compiler errors
  2. Test SET TEMP from National/Unicode
  3. Test SET TEMP from Raw
  4. Test SET TEMP from Literal
  5. Test SET TEMP into National/Unicode
  6. Test SET TEMP into Raw

Bugs

  1. SET TEMP into a Raw Alpha does not appear to set any characters. * FIXED * March 28 engine
  2. Process Compiler does not report errors when using Group fields. Executing the SET TEMP with group fields will cause input to crash or hang on exit.

  -- SteveFrizzell - 2011-03-08 \ No newline at end of file
View topic | History: r8 < r7 < r6 < r5 | More topic actions...
 
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