kconfig: clean up EOF handling in the lexer
A new file should always start in the INITIAL state. When the lexer bumps into EOF, the lexer must get back to the INITIAL state anyway. Remove the redundant <<EOF>> pattern in the PARAM state. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
This commit is contained in:
parent
cc66bca775
commit
0bcc547ec4
|
@ -178,9 +178,6 @@ n [A-Za-z0-9_-]
|
||||||
\\\n ;
|
\\\n ;
|
||||||
[[:blank:]]+
|
[[:blank:]]+
|
||||||
. warn_ignored_character(*yytext);
|
. warn_ignored_character(*yytext);
|
||||||
<<EOF>> {
|
|
||||||
BEGIN(INITIAL);
|
|
||||||
}
|
|
||||||
}
|
}
|
||||||
|
|
||||||
<STRING>{
|
<STRING>{
|
||||||
|
@ -262,6 +259,8 @@ n [A-Za-z0-9_-]
|
||||||
}
|
}
|
||||||
|
|
||||||
<<EOF>> {
|
<<EOF>> {
|
||||||
|
BEGIN(INITIAL);
|
||||||
|
|
||||||
if (current_file) {
|
if (current_file) {
|
||||||
zconf_endfile();
|
zconf_endfile();
|
||||||
return T_EOL;
|
return T_EOL;
|
||||||
|
|
Loading…
Reference in New Issue