|
Rules Syntax Checker, @7 |! z' ~. z5 {$ ?( K Z8 v
The rules_syntax_checker is a utility you can run on a rule file to validate the syntax of its: k4 ^- m3 {# f, N) Y
statements. The full path to this executable is
# }# |: U7 u1 E' ]3 I$MGC_HOME/shared/pkgs/icv.${VCO}/tools/misc/rules_syntax_checker. As shown in the
8 M1 c' T# y& ^following example, this utility prompts you for the name of the rule file and then runs the check.
& I2 X4 k( L! s& v9 KIt creates a zero length file named “compiled” if you answer “y(es)”.
$ j1 N& {( D N. L# v U" V4 K/ p) vrules_syntax_checker8 `- H; B( l+ @6 c/ {1 ~
Please input the file name (CTRL-D to abort): rule_file; J3 T9 f. R) Z' @' }; s
13-72 Calibre Verification User’s Manual
% ^" L9 k% }& zUtilities/ ^9 t3 M( Y' T. X- {0 B
Rules Syntax Checker
2 L& w: V' w; g, Q& a' t* bSuccessful compilation; compilation time = 0.02
, C$ K/ R0 R. f4 T. FYou can also specify the pathname to the rule file upon invocation, as follows:" X+ b* E: s( ?6 [8 K
rules_syntax_checker rule_file
& o, u+ O* b& e( o- \5 S* t8 m! ^% OYou may want to do this if you are writing a shell script to automate the process.( V5 c8 v5 ?+ W
Encountering an error terminates the check. The rule file compiler generates an error message5 \6 N% j2 |% i; {- ~
for the first such mistake it finds where the offending word sequence appears in the error' x0 I' i" `$ }) H
message. For example:6 g' A' |& {7 f9 X5 t' s# Y/ t
Error INP1 on line 15 of rule_file - superfluous or invalid input object:
- b+ m+ O' p5 a I$ {SORCE.
2 E+ ?4 X2 F7 ?) tAfter correcting the first such error, recheck the rule file to find the next error. Repeat this
7 U- B$ x$ Q. j x8 a( u0 T8 Wprocess until the rule file generates no syntax errors. |
|