Fetching examples

In this example, VRL has a Test field that contains three sub-fields. The sub-field separator character is “-”.

Field "Test2" does not have any sub-fields.

The input content is:

Test: >A-B-C<
		Test2: >D<

One source and one destination

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

Before CIS 6.0, @tmp was . Only the first sub-field was copied.>A<

After CIS 6.0, @tmp is >A-B-C<. The entire field content is copied.

Two sources and two destinations

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

Before CIS 6.0:

  • @tmp was >>A<.
  • Only the first sub-field was copied.
  • The @tmp was >B<.
  • The second sub-field was copied to this destination, which was the content of field Test2(D).

After CIS 6.0:

  • @tmp is >A-B-C<.
  • The entire field content is copied. The @tmp2 is >D<.
  • The content of field Test2 content is copied.

xlateInVals

The content of xlateInVals in Pre Proc is updated.

    { { 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 sub-field’s content to variables a,b, and 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 and c empty strings.

This now displays:

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

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