XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''"> Interpreting Session and Journal Files
As can be seen above in the example above that discusses hard coded path and file names in journal and session files, many of the arguments passed to PCL functions are listed as literal values in the journal and session files. Literal strings are always set off with double quotes (“). Arguments that appear to be arrays of integers can be literal strings set off with double quotes. The strings in that case are usually a list of points or vectors:
STRING asm_create_hpat_xyz_created_ids[VIRTUAL]
asm_const_hpat_xyz(“1”, “<1 1 1>”, “[0 0 0]”, @
“Coord 0”, @
asm_create_hpat_xyz_created_ids)
In this example:
“1” | is a string literal containing the character 1. |
“<1 1 1>” | is a string literal containing the description of a vector. |
“[0 0 0]” | is a string literal containing the description of a point. |
“Coord 0” | is a string literal containing the description of a coordinate frame. |
and:
elementprops_create(“ps1”, 71, 25, 30, 1, 1, 20, @
[13, 21, 4124, 4126, 4125],
In this example fragment, the eighth argument, [13, 21, 4124, 4126, 4125], is an array of five integers.
If you are in doubt about the interpretation of a literal argument in a journal or session file, the argument can be passed to the PCL command “dump”, which will list what kind of argument has been passed in the history window.
For example:
dump “[0 0 0]” | will report STRING[7] = “[0 0 0]” |
dump [0 0 0] | will report INTEGER(3) = [0, 0, 0] |
dump <0 0 0> | will report “Missing operand to expression” indicating that this is an invalid argument. |
The “dump” command can be a powerful tool to help better understand the contents of a journal or session file.