From: mapson AT mapson DOT com (Mapson)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Flex- small problem
Date: Tue, 16 Jun 1998 13:41:06 GMT
Organization: Yale University
Lines: 17
Message-ID: <358672d0.510293@news.cis.yale.edu>
References: <35842d90 DOT 8605608 AT babyblue DOT cs DOT yale DOT edu> <3584A433 DOT 47F8891D AT alcyone DOT com>
NNTP-Posting-Host: logan.eng.yale.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Thanks, Nate and Erik, for your assistance. This does indeed do the
job:

From the flex info:

>    If you do not supply your own version of `yywrap()', then you must
>    either use `%option noyywrap' (in which case the scanner behaves as
>    though `yywrap()' returned 1), or you must link with `-lfl' to
>    obtain the default version of the routine, which always returns 1.

And the main point of yywrap(), far as I can tell, is to allow you to
allow for the possibility of opening a new input file after the last
one EOFs.

Flex is amazing- I've wasted a lot of time in the past writing
context-specific code to do subsets of what it does generically (and
fast).