|
Rules Syntax Checker8 {; Z% E" e+ G. f' M1 ~
The rules_syntax_checker is a utility you can run on a rule file to validate the syntax of its$ A+ g6 p/ `2 O! k! X! f
statements. The full path to this executable is
" V5 A) i9 B0 ~4 N" {8 K$MGC_HOME/shared/pkgs/icv.${VCO}/tools/misc/rules_syntax_checker. As shown in the: |) y/ e7 K4 Z: w u
following example, this utility prompts you for the name of the rule file and then runs the check.( m6 h) G3 u, R0 o9 Y' \" Z
It creates a zero length file named “compiled” if you answer “y(es)”.
( L. ?0 h# Y/ P3 I4 @rules_syntax_checker
6 ?6 N2 M4 e0 J7 DPlease input the file name (CTRL-D to abort): rule_file2 @ h2 [3 {( k3 M6 Z
13-72 Calibre Verification User’s Manual
- ^" g# B0 t$ `6 {% B6 JUtilities4 e1 q2 V4 U! X# S
Rules Syntax Checker
: w( E1 ^9 b! c6 JSuccessful compilation; compilation time = 0.02; w+ N( l: ^# M3 u1 |8 W5 p \
You can also specify the pathname to the rule file upon invocation, as follows:$ n+ f, y* P, V& @" a/ z* v
rules_syntax_checker rule_file
9 I5 f% a s% u1 T0 PYou may want to do this if you are writing a shell script to automate the process.) t/ B8 ~. B- L: Q' n
Encountering an error terminates the check. The rule file compiler generates an error message
( a( T% W+ _0 _# w/ l( x; dfor the first such mistake it finds where the offending word sequence appears in the error
! W8 m, s; T7 cmessage. For example: b$ i* U% ^, d( d
Error INP1 on line 15 of rule_file - superfluous or invalid input object:
! B. d& @8 a7 m, CSORCE.
7 C# e. s7 J- v3 H/ x1 x, |8 jAfter correcting the first such error, recheck the rule file to find the next error. Repeat this
/ K" i; @9 h7 T4 ]4 E, G: r) rprocess until the rule file generates no syntax errors. |
|