|
Rules Syntax Checker
z Y7 m) w: D) {4 l/ PThe rules_syntax_checker is a utility you can run on a rule file to validate the syntax of its" w1 `: f& d X& {" y, i* D, l
statements. The full path to this executable is
$ [$ C$ Z# X' B0 [/ ]8 E% s$MGC_HOME/shared/pkgs/icv.${VCO}/tools/misc/rules_syntax_checker. As shown in the
! o! d- o5 n" Z6 G* ~1 m/ Xfollowing example, this utility prompts you for the name of the rule file and then runs the check., d% }) m: \( L( n' g1 w6 U
It creates a zero length file named “compiled” if you answer “y(es)”.
: K: p+ L- n6 l% N$ Vrules_syntax_checker
$ M9 l6 S: A, e3 w- nPlease input the file name (CTRL-D to abort): rule_file( O9 r2 w( }8 v
13-72 Calibre Verification User’s Manual5 [( i% q5 T$ \" `8 Q4 }2 q2 B8 B
Utilities
( d* c4 n% e- m+ uRules Syntax Checker
. U7 K0 {+ X( }/ vSuccessful compilation; compilation time = 0.02! ? ?! O7 B/ }2 s
You can also specify the pathname to the rule file upon invocation, as follows:* W4 R# m! n( r S7 E% x
rules_syntax_checker rule_file
; K4 i2 B) ?7 `: H2 _You may want to do this if you are writing a shell script to automate the process.
9 \, H. \6 f& b' f2 g! ^Encountering an error terminates the check. The rule file compiler generates an error message
8 t- T. f! m7 K1 L4 E9 ffor the first such mistake it finds where the offending word sequence appears in the error
4 X3 N# t& s* f1 x0 |7 o4 ?% W: zmessage. For example:
: g+ b" F; F* |- C5 hError INP1 on line 15 of rule_file - superfluous or invalid input object:) Y, f! }2 D' A: X2 I
SORCE.% z0 T) g( Y! m8 P
After correcting the first such error, recheck the rule file to find the next error. Repeat this5 k' v/ V- G4 ~
process until the rule file generates no syntax errors. |
|