On Mon, 13 Oct 2008, Jim Michaels wrote:
> fgets & fgetc stops when it reaches a ^z character (eof character) ^d on
> unix. the batch mode flex does not I think do this, because it uses fread.
> however, it might if you open the file in text mode instead of binary.
> If you happen to want to
On Mon, 13 Oct 2008, Jim Michaels wrote:
> "0" "END"
> (ZERO T_END) happen to be in the lexer as part of a datum0 start sequence, of
> which there are multiple items, because they all start with a 0.
>
> as it stands, there is no way to end with a
>
>
> start : code0 code2 tagged_format ;
am using bison 2.1, flex version 2.5.4 - I have no choice about using anything
newer for now (using gnuwin32), but it would be nice to know if a bug is fixed
in a newer version.
Q1. do I always need to write a driver for a C++ parser/lexer combo?
Q2. I haven't gotten a C++ version of the parser
fgets & fgetc stops when it reaches a ^z character (eof character) ^d on unix.
the batch mode flex does not I think do this, because it uses fread. however,
it might if you open the file in text mode instead of binary.
If you happen to want to lex a ^z or ^d this can be a problem!
will I need t
