using new and delete instead,
> now that I am using C++?
> bison is causing its own problems by messing with malloc and free.
>
>
> Jim Michaels
> [EMAIL PROTECTED]
> http://JesusnJim.com
>
>
>
>
> - Original Message
> From: Laurence Finston &
lems with programs is when somebody starts messing with
these.
and I need malloc and free. maybe I should be using new and delete instead,
now that I am using C++?
bison is causing its own problems by messing with malloc and free.
Jim Michaels
[EMAIL PROTECTED]
http://JesusnJim.com
----- Ori
On Mon, 13 Oct 2008, Jim Michaels wrote:
> as I basically said before, My stack and dequeue template class is
> written in C++.
I didn't understand this. I thought you might have meant that
you needed some features from the C++ parser class.
> I could possibly rewrite it in C (why?), but my
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 ;
ED]
http://JesusnJim.com
- Original Message
From: Laurence Finston <[EMAIL PROTECTED]>
To: Jim Michaels <[EMAIL PROTECTED]>
Sent: Monday, October 13, 2008 3:30:23 AM
Subject: Re: problems with bison-flex
Another thing is that I had to redefine `YY_INPUT' as explained in
On Fri, 10 Oct 2008, Jim Michaels wrote:
> flex is hitting end of file and yyparse always returns 1, error in input.
> The last strings in the file is always
> 0
> EOF
>
> which is the tokens ZERO T_EOF. they are expected in the parser.
> I even tried returning 0 in yylex when it saw "EOF". n
