On 21 Jun 2007, at 20:07, Fernando Ferreira wrote:
Just another question: is the path to the skeleton hardcoded to
$PREFIX/share/bison/ ? I tried to pass --skeleton="/home/foo/
bar.cc" but it didn't work. Thanks :D
Please to take down the CVS version, as this has changed lately. The
latest
Hans Aberg wrote:
On 21 Jun 2007, at 11:26, Hans Aberg wrote:
In order to make it simple for you, you might add a macro in the
skeleton file. One variation might be (don't remember) to add a macro
something like b4_prereduction_code and then use in the .y file
%define prereduction_code {...}
On 21 Jun 2007, at 11:26, Hans Aberg wrote:
In order to make it simple for you, you might add a macro in the
skeleton file. One variation might be (don't remember) to add a
macro something like b4_prereduction_code and then use in the .y
file %define prereduction_code {...} (or %define
On 21 Jun 2007, at 08:36, Fernando Ferreira wrote:
Yes, and that would work, but them every time I recompile the .yy
file with bison I would have to manually change the .cc to
include the modification. That's why I think it would be helpful
to have a macro similar to flex' YY_USER_ACTION, s
Hans Aberg wrote:
On 20 Jun 2007, at 20:12, Fernando Ferreira wrote:
I have you tried to put it into yacc.c, somewhere between
"yyreduce:" and "switch (yyn)"?
Yes, and that would work, but them every time I recompile the .yy
file with bison I would have to manually change the .cc to include
On 20 Jun 2007, at 20:12, Fernando Ferreira wrote:
I have you tried to put it into yacc.c, somewhere between
"yyreduce:" and "switch (yyn)"?
Yes, and that would work, but them every time I recompile the .yy
file with bison I would have to manually change the .cc to include
the modificatio
Evan Lavelle wrote:
Fernando Ferreira wrote:
The reason for my request is that, as bison generates LR parsers,
there is no way to, for instance, execute an action before a rule is
reduced, only after.
I've never tried an action at the start of a rule, but I'm pretty sure
that you can do it.
Fernando Ferreira wrote:
The reason for my request is that, as bison generates LR parsers, there
is no way to, for instance, execute an action before a rule is reduced,
only after.
I've never tried an action at the start of a rule, but I'm pretty sure
that you can do it. Look up 'embedded ac
Hans Aberg wrote:
On 20 Jun 2007, at 12:28, Fernando Ferreira wrote:
I'm a huge fan of this project and I'm using it for several of my
small personal project (hopefully one day I will get to finish and
publish one of them). I use both flex and bison C++ Language
Interface (not that it has any
On 20 Jun 2007, at 12:28, Fernando Ferreira wrote:
I'm a huge fan of this project and I'm using it for several of my
small personal project (hopefully one day I will get to finish and
publish one of them). I use both flex and bison C++ Language
Interface (not that it has anything to do with
Good morning!
I'm a huge fan of this project and I'm using it for several of my small
personal project (hopefully one day I will get to finish and publish one
of them). I use both flex and bison C++ Language Interface (not that it
has anything to do with the feature I'm about to request) and o
On 15 Mar 2007, at 16:34, Matt Cupp wrote:
I was wondering if there is currently a way to include other files in
a Bison source file at run time? Like C/C++'s #include preprocessor
directive. If not is this something I could add to feature requests?
(You probably mean compile time - "run tim
Hi,
I was wondering if there is currently a way to include other files in
a Bison source file at run time? Like C/C++'s #include preprocessor
directive. If not is this something I could add to feature requests?
Thanks,
Matt Cupp
___
help-bison@gnu.
On 30 Oct 2006, at 06:56, Bob Smith wrote:
Satya points out the --report=conflict-path reference in the TODO
file is exactly what I wanted.
I am not sure this is what you asked for. The paper by DeRemer and
Penello is just a method of computing efficient LALR(1) lookahead
sets; perhaps wh
On 10/29/2006 7:18 AM, Hans Aberg wrote:
The problem is that you need to find someone willing to do the
implementation. And if all developers are heavy busy doing things to
them more important, why would they bother implementing it? :-) Your
idea seems to be along the line, if the compiler find
Satya is developing a GUI for displaying Bison grammars, I think, so
you might explain your ideas to him.
Hans Aberg
hi,
I am experimenting with various possibilities of helping people understand
Bison (and parsing in general) better. I have currently implemented a gdb
style interactive
The problem is that you need to find someone willing to do the
implementation. And if all developers are heavy busy doing things to
them more important, why would they bother implementing it? :-) Your
idea seems to be along the line, if the compiler finds an error of a
function, and display
On 10/28/2006 3:56 PM, Hans Aberg wrote:
On 27 Oct 2006, at 19:42, Bob Smith wrote:
When Bison encounters a S/R or R/R error, it would be helpful if it
could also write to the output file an input stream which would
trigger the error.
That way, the user could run the input stream through the
On 27 Oct 2006, at 19:42, Bob Smith wrote:
When Bison encounters a S/R or R/R error, it would be helpful if it
could also write to the output file an input stream which would
trigger the error.
That way, the user could run the input stream through the grammar
so as to better understand th
When Bison encounters a S/R or R/R error, it would be helpful if it
could also write to the output file an input stream which would
trigger the error.
That way, the user could run the input stream through the grammar so
as to better understand the problem. As it is, we're told in which
state
20 matches
Mail list logo
