Difference: UnicodeRUNStmt (4 vs. 5)

Revision 52011-06-15 - JeanNeron

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

RUN Statement

Line: 36 to 36
 
  1. Test --- STREAM OPEN with a pipe (implied RUN)

Bugs

Changed:
<
<
  1. Implementation difference. The command is always encoded into UTF-8, not the the encoding of the OS shell.
  2. RUN with passing any field of any type causes problems (C-asserts, or * glibc detected * free(): invalid next size (normal): 0x09d4ae20 ***g) if you run it twice. Run the RUN subroutine in TST to see the errors.
>
>
  1. Implementation difference. The command is always encoded into UTF-8, not the the encoding of the OS shell.
  2. RUN with passing a National field causes seg fault if you run it repeatedly.
  3. RUN with passing a Unicode field causes strange & inconsistent things to happen if you run it repeatedly.
 
  1. PASSing a unicode field via RUN doesn't seem to work, ie, echo $1 >some.file where $1 was a unicode field containing "This is Uni data\u03a3" does not give the expected result in the file (should contain a Σ symbol).

-- PeteBrower - 2011-03-17 \ 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