Hello all:
The fastest way to read textual data is to write your own scanner
using lex/flex, and to ensure that it doesn't need to back-up (see the
flex info file for what backing-up is and how to avoid it).
I've used flex. Now I am parsing the file and recognizing tokens.
My structure is
The fastest way to read textual data is to write your own scanner
using lex/flex, and to ensure that it doesn't need to back-up (see the
flex info file for what backing-up is and how to avoid it).
Just adding that it may (or may not) be a good idea to use lex/flex in
combination with
Niels Hald Pedersen wrote:
The fastest way to read textual data is to write your own scanner
using lex/flex, and to ensure that it doesn't need to back-up (see the
flex info file for what backing-up is and how to avoid it).
Just adding that it may (or may not) be a good idea to use
On Wed, 9 Sep 1998 17:17:02 Glynn Clements wrote:
Niels Hald Pedersen wrote:
The fastest way to read textual data is to write your own scanner
using lex/flex, and to ensure that it doesn't need to back-up (see the
flex info file for what backing-up is and how to avoid it).
Hello all,
I have files of the following formats:
Name
Company
day
month
year
job_name time max min flag1 flag2 flag3 flag4 job_name
job_name time max min flag1 flag2 flag3 flag4 job_name
job_name time max min flag1 flag2 flag3 flag4 job_name
Ibrahim F Haddad wrote:
I have files of the following formats:
Name
Company
day
month
year
job_name time max min flag1 flag2 flag3 flag4 job_name
job_name time max min flag1 flag2 flag3 flag4 job_name
job_name time max min flag1 flag2 flag3 flag4 job_name
