|
Rules Syntax Checker
# z4 m$ J8 S5 q) d$ m9 tThe rules_syntax_checker is a utility you can run on a rule file to validate the syntax of its' U w7 M$ {: @
statements. The full path to this executable is
1 N6 Y9 b& q0 { |$MGC_HOME/shared/pkgs/icv.${VCO}/tools/misc/rules_syntax_checker. As shown in the6 K; }1 G$ [4 m2 O3 B. q
following example, this utility prompts you for the name of the rule file and then runs the check.# V: a4 Z* x2 ]
It creates a zero length file named “compiled” if you answer “y(es)”.
3 K- [. m' r' U# w( d) n4 nrules_syntax_checker+ |4 x# a8 t9 N" {
Please input the file name (CTRL-D to abort): rule_file. x9 t# v* Q" m: S/ j0 v
13-72 Calibre Verification User’s Manual( U# Y( ]1 \, J, j1 e- O7 q
Utilities
; K- ]9 ~" D0 j- g" x1 H/ U) [( YRules Syntax Checker9 G: s- Z7 P, v$ d9 @3 p2 a, H
Successful compilation; compilation time = 0.029 P; O4 z, g6 j' T! c7 U. h0 w- m; J
You can also specify the pathname to the rule file upon invocation, as follows:
! @2 G& ?% E+ O4 Urules_syntax_checker rule_file9 ~8 q. z+ ~0 g+ _* n
You may want to do this if you are writing a shell script to automate the process.
2 ?, c1 c8 e7 U! O: Z" T# G* lEncountering an error terminates the check. The rule file compiler generates an error message
1 X5 g2 R' B2 J' a1 rfor the first such mistake it finds where the offending word sequence appears in the error) z u, V+ e$ @# c7 r; m: t
message. For example:" ~7 G$ S" m u" z/ S
Error INP1 on line 15 of rule_file - superfluous or invalid input object:/ ^9 c& E& Z" X( S* v$ G/ A
SORCE.
( K* ^; }' N$ d }! S. h5 M FAfter correcting the first such error, recheck the rule file to find the next error. Repeat this
/ D1 C X1 Y) Vprocess until the rule file generates no syntax errors. |
|