|
Rules Syntax Checker- s4 M& ^2 S1 W5 l+ e/ g
The rules_syntax_checker is a utility you can run on a rule file to validate the syntax of its& W5 Q( y6 I3 T& N9 |/ A
statements. The full path to this executable is) Z7 s/ m# k2 N- R+ b- q
$MGC_HOME/shared/pkgs/icv.${VCO}/tools/misc/rules_syntax_checker. As shown in the
; z( V6 P) ~6 ifollowing example, this utility prompts you for the name of the rule file and then runs the check.
" S( E, q: l$ H/ bIt creates a zero length file named “compiled” if you answer “y(es)”.
$ K& N4 j/ Y( I/ X; Lrules_syntax_checker
9 H/ c7 G% S7 p5 ^9 C' bPlease input the file name (CTRL-D to abort): rule_file4 G+ s# [( q( Q
13-72 Calibre Verification User’s Manual: S( v$ ^; i( I* s. ?. d
Utilities; G2 i3 e3 Y% E) T! }4 x- s8 m' r
Rules Syntax Checker
5 X2 p( }$ J- t8 @) @: ZSuccessful compilation; compilation time = 0.020 F6 u7 b- d* B* L
You can also specify the pathname to the rule file upon invocation, as follows:
4 e& c# [! w' x( orules_syntax_checker rule_file
Y6 o2 n1 E/ IYou may want to do this if you are writing a shell script to automate the process.% n- d6 a" [ [. A F, a
Encountering an error terminates the check. The rule file compiler generates an error message
; W5 ^1 y/ A+ pfor the first such mistake it finds where the offending word sequence appears in the error j2 w+ g" r) c8 ?' T
message. For example:
2 z0 `' a8 Q8 eError INP1 on line 15 of rule_file - superfluous or invalid input object:$ U4 e9 z. U& H7 L% m0 P3 |* `
SORCE.
* j7 U1 i$ m9 Q4 TAfter correcting the first such error, recheck the rule file to find the next error. Repeat this# s8 ^6 n6 d: U1 c
process until the rule file generates no syntax errors. |
|