Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.compilers > #2522

What happens at the end of the file for lex?

Show all headers | View raw

I wonder what is supposed to happen when a lex lexer reaches the end of
the input calling input().

The only information I found in the flex 2.6.4 manual states:

If 'input()' encounters an end-of-file the normal 'yywrap()' processing
is done.  A "real" end-of-file is returned by 'input()' as 'EOF'.

What is the difference between an "end-of-file" and a "'real' end-of-file"?

I did a quick test using this .lex file:


%%
.       {for(int i = 0; i < 8; i++) {int ch = input(); printf("%d\n", ch);}}

%%
main()
        {
        yylex();
        }

And using a single-character input-file, I see:

philipp@notebook5:/tmp$ ./a.out < test.c
10
0
0
0
0
0
0
0

So apparently input() just returns 0 (and keeps doing so).

Is input() supposed to always return 0 at the end? Could inut() return 0
in some other situation? When would input() return EOF?

Philipp
[The convention in lex and flex is that input() returns 0 at tne end of input.
You can use a <<EOF>> rule if you want your lexer to do something other than return
when it gets to EOF.  The yywrap() routine is used for file switching if your lexer
handles multiple input files in a single run. -John]

Back to comp.compilers | Previous | Next — Next in thread | Find similar

Thread

What happens at the end of the file for lex? Philipp Klaus Krause <pkk@spth.de> - 2020-06-03 10:04 +0200
  Re: What happens at the end of the file for lex? Philipp Klaus Krause <pkk@spth.de> - 2020-06-04 19:16 +0200

csiph-web