COPY example: Two sources and two destinations

{ { OP COPY } 
        { ERR 0 }
        { IN {Test Test2}  }
        { OUT {@tmp @tmp2} }
}     

Before CIS 6.0:

  • The @tmp was: >A<.

    Only the first subfield was copied.

  • The @tmp2 was: >B<.

    The second subfield was copied to this destination, which is expected to be the content of field Test2(D).

After CIS 6.0:

  • The @tmp is: >A-B-C<.

    The whole field content is copied.

  • The @tmp2 is: >D<.

    The content of field Test2 content is copied.

The content of xlateInVals in Pre Proc has also been updated:

  • Before CIS 6.0, xlateInVals was a list.
  • After CIS 6.0, xlateInVals is a string.
 { { OP COPY }
        { ERR 0 }
        { PRE {
            #Note: Shows $xlateInVals
            puts "xlateInVals is: $xlateInVals"
            lassign $xlateInVals a b c
            puts "$a:$b:$c"
        }}
        { IN Test }
        { OUT @tmp_test }
    }     

Before CIS 6.0:

  • xlateInVals was list A B C.
  • Using lassign assigned the subfield’s content to variables a,b,c.

This displayed:

  • xlateInVals is: A B C
  • A:B:C

After CIS 6.0:

  • xlateInVals is a string A-B-C.
  • Using lassign assigns A-B-C only to variable a, and makes b,c empty strings.

This displays:

  • xlateInVals is: A-B-C
  • A-B-C::

This change happens on HRL/VRL/FRL and all HMD formats.