|
|
|
|
|
The tas command executes the Transaction Assembler (TAS) program to assemble script instructions.
Synopsis
tas [-c][-d][-e][-Iinclude_dir][-Ttalk_dir][-U name][-Dname[=def]][-H][-ooutfile][-ttas_preprocessor][-u size][-p][-w]infile
Description
The tas command is used to assemble script instructions recorded in an input file (infile) of the form application-name .t. It produces an executable file (outfile) of the form application-name .T , which is stored in a table as a list of executable script instructions.
The -e option requires exact string matches for speech phrases.
The arguments must be in the order given above for the command to work properly. The directory search specified by the arguments are: -I (include directory) and -T (talk directory).
Note:
No space is allowed between the -I and -T flags and their pathnames, but space is allowed after the -e flag. The -I option to tas is interpreted by cpp(1).
The remaining arguments are described in the following table:
Argument |
Description |
Comments |
-Uname |
Remove any initial definition of name |
Note that name is a reserved symbol that is predefined by the particular preprocessor. This option is interpreted by cpp(1). |
-Dname and -D name=def |
Define name with value def as if by a #define |
If no def is given, name is defined with value 1. The -D option has lower precedence than the -U option. If the same name is used in both a -U option and a -D option, the name is undefined regardless of the order of the options. This option is interpreted by cpp(1). |
-H |
Print, one per line on standard error, the path names of included files |
This option is interpreted by cpp(1) |
-ooutfile |
Name of the output file |
Default is out.T |
Note that the maximum number of literals per script allowed by the tas command is 450. If there are more than 450 literals in a script, the system displays the error message literal table overflow. Additional limitations enforced by the tas command are (whichever occurs first in a list file):
If more phrases are needed by an application, use multiple list files and tfile instructions within the script.
If your script contains a large number of define statements, tas may report messages such as the following during compilation:
script.t: 1068: too much defining
Here, script.t is the script source file, and 1068 is the line in which the define appears. The limit to the number of define statements that a script may have depends on the number of defined macros and their size. If this type of message appears, reduce the number of define statements in your script.
Files
/vs/bin/tas
Example
tas example.t
The program includes applicable header files and replaces literal definitions with corresponding numbers to produce an assembled version of the script. The assembled code is stored on disk under the label example.T . The unassembled instructions are found in the file /var/applN/trans/example.t.
tas example.t -I/var/include -T/var/speech
In addition to performing the same functions described for the previous example, tas checks the files in /var/include when processing include statements and the file in /var/speech when processing T-file statements.
