|
Rules Syntax Checker
, d; U8 _: v8 T$ Y+ bThe rules_syntax_checker is a utility you can run on a rule file to validate the syntax of its& o; G* f# b- ^! B$ ]4 j. K* h+ h3 @
statements. The full path to this executable is+ E7 R! {4 p" s* m* [2 z. Y, `2 U
$MGC_HOME/shared/pkgs/icv.${VCO}/tools/misc/rules_syntax_checker. As shown in the
, Y4 l; s0 o3 H9 zfollowing example, this utility prompts you for the name of the rule file and then runs the check.. T* A% N( |/ [6 @
It creates a zero length file named “compiled” if you answer “y(es)”.7 @* |) m% B5 q
rules_syntax_checker
9 ~2 S4 q4 j- W2 q; TPlease input the file name (CTRL-D to abort): rule_file* Z6 g! Y" d1 l$ d0 A- F
13-72 Calibre Verification User’s Manual
9 O$ I) p* i, b# ~Utilities7 t# S- I7 a; ^) s* Q1 T# p8 H, o
Rules Syntax Checker" X+ E$ |9 x( ^; f' A5 E
Successful compilation; compilation time = 0.02
. p3 S a k$ G9 e( X% ^3 W/ V: M x, ~; f/ ?You can also specify the pathname to the rule file upon invocation, as follows:' w: p8 b! y/ v9 Z
rules_syntax_checker rule_file
5 j! f5 [8 M6 r3 b7 [You may want to do this if you are writing a shell script to automate the process.
! b: t# H. I7 P! x' X$ ^Encountering an error terminates the check. The rule file compiler generates an error message' I5 p1 i' e( s$ b* C8 |
for the first such mistake it finds where the offending word sequence appears in the error, w# X3 [7 @; y; ]
message. For example:7 n. u4 c L9 G0 ]/ B
Error INP1 on line 15 of rule_file - superfluous or invalid input object:
1 e0 B- P7 |# L( h$ qSORCE.; m6 b' A8 s1 z8 [. J& ?2 B
After correcting the first such error, recheck the rule file to find the next error. Repeat this5 Z$ U/ F2 k7 q' l# N8 D
process until the rule file generates no syntax errors. |
|