|
Rules Syntax Checker
2 E9 p3 k7 E- Z1 B1 o2 {. `; w! cThe rules_syntax_checker is a utility you can run on a rule file to validate the syntax of its0 g, L A6 Q7 r& b3 q
statements. The full path to this executable is* a8 u0 b+ N4 b# u0 ]
$MGC_HOME/shared/pkgs/icv.${VCO}/tools/misc/rules_syntax_checker. As shown in the" o1 C6 i( ?9 ~: p: Q! O7 [
following example, this utility prompts you for the name of the rule file and then runs the check.
/ W4 x( Q# d2 H6 f8 i/ }( a s& sIt creates a zero length file named “compiled” if you answer “y(es)”.3 q* k! `/ w( j8 I9 d" ?
rules_syntax_checker
1 P* J, v$ O! `$ q& C5 D5 KPlease input the file name (CTRL-D to abort): rule_file
7 u( c+ Q# ^" ?) Z13-72 Calibre Verification User’s Manual
( A- r) S/ `/ XUtilities f- I% c6 i9 @6 ^' W
Rules Syntax Checker
/ z( M- w5 W. i+ \' z4 ?Successful compilation; compilation time = 0.023 E C1 d2 m0 k6 X! l0 d) C" x
You can also specify the pathname to the rule file upon invocation, as follows:
& \$ C% v" D% `( W1 P* }1 l/ e; i5 u- [rules_syntax_checker rule_file
1 h2 V5 h/ S( P- A& JYou may want to do this if you are writing a shell script to automate the process.
6 A/ _$ o+ C* S* E2 c- vEncountering an error terminates the check. The rule file compiler generates an error message1 i+ g& D4 B, c9 t" C
for the first such mistake it finds where the offending word sequence appears in the error2 G0 h8 [3 d0 N4 o
message. For example:
# n6 D% A! x" d% `9 R! LError INP1 on line 15 of rule_file - superfluous or invalid input object:# J, d% p7 v! a( P& V' V
SORCE.
8 f$ [, Y( a2 E( E+ m" iAfter correcting the first such error, recheck the rule file to find the next error. Repeat this
1 H8 h) a; P+ c0 v- xprocess until the rule file generates no syntax errors. |
|