--output and %output options

2009-08-01 Thread tys lefering
Hi, Running bison-2.4.1 from a script and using commandline options --output=file.c and --defines=file.h to know where the output is, it appears that if there are %output or %defines statements in the input grammar the output is written to other files. Would it not be better if the commandline opt

Re: --output and %output options

2009-08-01 Thread Joel E. Denny
On Sat, 1 Aug 2009, tys lefering wrote: > Would it not be better if the commandline options --output and > --defines override the settings from %output and %defines in the > grammar ? Yes. We've had many discussions about fixing that, but we've never done so. One problem is backward compatibil

Re: What are the arrays (yytranslate, yyprhs...) mean and how are they caculated in bison?

2009-08-01 Thread Joel E. Denny
On Fri, 31 Jul 2009, bookman bookman wrote: > I am a newer in bison and i have used lex and bison to implement a > caculator. When i opened the source generated by bison, I found some arrays > instead of shift/reduce table and goto table, but i do not know what they > are stand for and how they a