On 11 Dec 2006, at 17:50, David Moriconi wrote:
I tried it and it seems to work but bison doesn't generate me a
new .c file. When i add the -S option and i start bison, all the
contents of my skeleton is printed in the DOS prompt. is that
because it does not work or it's normal?
Why do I
mand I ran: bison -d -l -S yyparse.c -o tcyacc.c TL1.y
Thank
From: Bob Rossi <[EMAIL PROTECTED]>
To: DaveMord <[EMAIL PROTECTED]>
CC: Help-bison@gnu.org
Subject: Re: Parser file
Date: Mon, 11 Dec 2006 11:32:32 -0500
On Mon, Dec 11, 2006 at 08:29:46AM -0800, DaveMord wrote:
>
On Mon, Dec 11, 2006 at 11:50:06AM -0500, David Moriconi wrote:
> I tried it and it seems to work but bison doesn't generate me a new .c
> file. When i add the -S option and i start bison, all the contents of my
> skeleton is printed in the DOS prompt. is that because it does not work or
> it's
and i saw somwhere to replace .y by the parser
> file name (yyparse.c in my case) But this doesn't work (no such file or
> directory named TL1.yyparse.c )
Hi,
I have push.c in the share/bison directory. If I do
'bison -S push.c', th
Hi
we implemented our yyparse in yyparse.c file. I want to know how to indicate
to Bison to take this file as template. I tried : bison -d -l -o tcyacc.c
TL1.yyparse.c
My yac file is named: TL1.y and i saw somwhere to replace .y by the parser
file name (yyparse.c in my case) But this doesn&#
Le 21 août 06 à 20:42, Joel E. Denny a écrit :
On Sun, 20 Aug 2006, Frans Englich wrote:
Any chance that %defines can be changed to also allow the name to be
explicitly specified?
I'm not sure why %defines and -d and are different from --defines, -o,
--output, and %output. Reading the -d a
On Sun, 20 Aug 2006, Frans Englich wrote:
> Any chance that %defines can be changed to also allow the name to be
> explicitly specified?
I'm not sure why %defines and -d and are different from --defines, -o,
--output, and %output. Reading the -d and --defines documentation makes
it seem inten
On Monday 31 July 2006 16:19, Joel E. Denny wrote:
> On Mon, 31 Jul 2006, Frans Englich wrote:
> > Yeah, still don't see how it would be possible to call the output files
> > QueryTransformer.cpp/QueryTransformer.h. Specifying -o
> > QueryTransformer.cpp and --defines leads to
> > QueryTransformer.
On Mon, 31 Jul 2006, Frans Englich wrote:
> Yeah, still don't see how it would be possible to call the output files
> QueryTransformer.cpp/QueryTransformer.h. Specifying -o QueryTransformer.cpp
> and --defines leads to QueryTransformer.cpp/QueryTransformer.hpp.
info bison and search for --defin
On Sunday 30 July 2006 16:30, Joel E. Denny wrote:
> On Sat, 29 Jul 2006, Frans Englich wrote:
> > The sed calls remove the defines for the YYTOKENTYPE so I can use the
> > enum without trouble.(yytokentype).
>
> This is fixed in CVS, so you should see it in Bison 2.4.
Nice!
> > Can I do these re
On Sat, 29 Jul 2006, Frans Englich wrote:
> The sed calls remove the defines for the YYTOKENTYPE so I can use the enum
> without trouble.(yytokentype).
This is fixed in CVS, so you should see it in Bison 2.4.
> Can I do these renames with bison directives? I would prefer if my .ypp file
> was
I don't see how it helps me since I don't want
> > to
> > change the "QueryTransformParser" part. Then there is "%output" which the
> > Bison manual says "set the name of the parser file." I don't get what
> > that means, or how it
o
change the "QueryTransformParser" part. Then there is "%output" which the
Bison manual says "set the name of the parser file." I don't get what that
means, or how it differs from %file-prefix.
I already specify %defines and %name-prefix. I'm positive towards
13 matches
Mail list logo
