Fixed spurious syntax errors for including files that don't begin with

a SEMICOLON token (a newline or semicolon, or one of these preceded
by a comment and/or whitespace).  The input stream was switched too
early and the parser was expecting a SEMICOLON in the included file
instead of after the filename in the include directive.

Submitted by:	Stefan Farfeleder <stefan@fafoe.narf.at>
Kept alive by:	Adam C. Migus <adam@migus.org>
This commit is contained in:
Bruce Evans 2003-11-14 11:23:25 +00:00
parent 33a3109794
commit e3937b620a
1 changed files with 4 additions and 3 deletions

View File

@ -118,6 +118,9 @@ Spec:
|
Config_spec SEMICOLON
|
INCLUDE ID SEMICOLON
= { include($2, 0); };
|
SEMICOLON
|
error SEMICOLON
@ -164,9 +167,7 @@ Config_spec:
= {
hints = $2;
hintmode = 1;
} |
INCLUDE ID
= { include($2, 0); };
}
System_spec:
CONFIG System_id System_parameter_list