REN is (, variable is [a-zA-Z]+ and CLOSED_PAREN is ).
I want ONLY "gdb" to be allowed in this variable context.
Is there a way to force the syntax error in the action in such a way
that bison then bubbles up the error into the above 'output' error r
On Fri, Oct 03, 2014 at 10:18:18PM -0400, Bob Rossi wrote:
> Hi,
>
> I'm trying to get 100% coverage on my bison grammar actions using gcov.
>
> I noticed i'm having difficulty getting the %destructor actions to be
> called, which made me realize that perhaps I&#x
the %destructor for
list which result called. Correct?
It would be really nice if Bison could tell you all the symbols that
need a potential %destructor, does it do that?
Thanks,
Bob Rossi
___
help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
On Thu, Sep 25, 2014 at 09:31:02PM -0400, Bob Rossi wrote:
> Hi,
>
> I'm writing a pure bison push parser in C.
>
> I've unit tested the parser well, but now I'm starting to unit test
> it when the parser has a syntax error. This has proved challenging.
>
>
On Sat, Sep 27, 2014 at 12:23:37AM +0200, Hans Aberg wrote:
>
> > On 26 Sep 2014, at 21:58, Bob Rossi wrote:
> >
> > On Fri, Sep 26, 2014 at 03:37:18PM +0200, Hans Aberg wrote:
>
> >>> The %destructor for result and result_list does not call free, but
&
On Fri, Sep 26, 2014 at 03:37:18PM +0200, Hans Aberg wrote:
> > On 26 Sep 2014, at 03:31, Bob Rossi wrote:
>
> > A secondary concern I had with %destructor is how it worked when lists
> > are used in the bison grammar. I'm concerned about a double free. For
> &
, and the result's next
pointer, and so on.
Is it correct for me to call gdbmi_result_free($$) instead of free($$)?
If so, does the bison language ensure that the variable destructor won't
also get called, which could result in a double free of the variable?
t would be nice if we made this available to the autoconf
people, because, others are going to need this.
Thanks,
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
> Any ideas?
Add a full expression, fexpr, that can either be nothing, or an
expression.
Same with the assignment. However, an assignment is an expression, so I
think you shouldn't separate them out.
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On Wed, Feb 20, 2008 at 01:25:36PM -0500, Joel E. Denny wrote:
> On Wed, 20 Feb 2008, Bob Rossi wrote:
>
> > Sorry for the extremely long delay. I'm trying out your suggestion now.
> > Whenver I put a struct in the parse param like so,
> > %parse-param { struct gdb
On Sun, Sep 09, 2007 at 11:03:13AM +0200, [EMAIL PROTECTED] wrote:
> > On Sat, 8 Sep 2007, Bob Rossi wrote:
> >> The second issue is slightly more fuzzy. Essentially, after each token I
> >> give to the parser, it would probably be useful to know if it just
> >> f
On Tue, Feb 19, 2008 at 09:22:38PM -0500, Bob Rossi wrote:
> On Tue, Feb 19, 2008 at 07:54:16PM -0500, Joel E. Denny wrote:
> > On Tue, 19 Feb 2008, Claudio Saavedra wrote:
> >
> > > El mar, 19-02-2008 a las 19:21 -0500, Joel E. Denny escribió:
> > > >
&g
ks. It seems I can't use grep correctly this week.
OK, it works now. Thank you.
Hopefully I'll find some time soon to try out the new changes.
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
#x27;
make[1]: *** [bison-runtime.pot] Error 2
make[1]: Leaving directory `/home/bob/rcs/cvs/bison/trunk/bison/runtime-po'
make: *** [all-recursive] Error 1
Any idea?
Thanks,
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On Tue, Jan 22, 2008 at 05:00:54PM +, Daniel Kraft wrote:
> Bob Rossi wrote:
>>>>> start_symbol:
>>>>> real_start_symbol
>>>>> {
>>>>> storeValueForProcession($1);
>>>>> YYACCEPT;
>>>>>
n the resulting configure related to gl_* symbols; I suspect that autoconf
> is missing some m4-files or the like?
Well, I've never attempted to do it manually. I just run the script
'bootstrap'. I haven't done this in a few months, so, hopefully it's
still the same.
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
t call to yyparse()?
Aha, Yes!
Use the push parser that I have just implemented in Bison. You will be
the first beta tester. The documentation should be in CVS and you need a
CVS version of bison.
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
x27;d want to tell the parser
that it's done after I've finished an "output_list" rule.
It is possible that I can workaround these issues by changing the
grammar or moving where I do the assignment to the 'tree' pointer.
However, these issues will probably come up again
yypush_parse (yyps_local);
} while (yystatus == YYPUSH_MORE);
so I'm thinking the only point it would end is when the grammar is
finished. That is yystatus != YYPUSH_MORE.
I think it should allow the user to break out on certain circumstances?
Am I missing something?
On Mon, Jul 30, 2007 at 08:56:53PM -0400, Joel E. Denny wrote:
> On Mon, 30 Jul 2007, Bob Rossi wrote:
>
> > OK, so, when I compile gdbmi grammar with push-pull-parse and with
> > pure-parse I get a compile error. That's because in the generated c file
> > yypu
On Mon, Jul 30, 2007 at 08:50:32PM -0400, Joel E. Denny wrote:
> On Mon, 30 Jul 2007, Bob Rossi wrote:
>
> > > Again, the following seems more intuitive to me now:
> > >
> > > %define push_pull "pull" // default
> > > %def
On Mon, Jul 02, 2007 at 10:16:13AM -0400, Joel E. Denny wrote:
> On Mon, 2 Jul 2007, Bob Rossi wrote:
>
> > OK. I don't even know what push-pull-parser does. When I submitted the
> > patch, I only had support for push-parser and pure-parser didn't effect
> > it
On Mon, Jul 02, 2007 at 10:16:13AM -0400, Joel E. Denny wrote:
> On Mon, 2 Jul 2007, Bob Rossi wrote:
>
> > OK. I don't even know what push-pull-parser does. When I submitted the
> > patch, I only had support for push-parser and pure-parser didn't effect
> > it
and to the end of the file with the epilogue rule:
http://www.gnu.org/software/bison/manual/html_mono/bison.html#Epilogue
Any ideas?
Thanks,
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On Sun, Jul 01, 2007 at 08:30:17PM -0400, Joel E. Denny wrote:
> On Mon, 25 Jun 2007, Bob Rossi wrote:
> > In a few of these, it describes the
> > difference when the push parser option is used. I can't really remember
> > how you eventually got the push parser w
On Mon, Jun 18, 2007 at 09:25:52PM -0400, Joel E. Denny wrote:
> On Mon, 18 Jun 2007, Bob Rossi wrote:
>
> > On Mon, Jun 11, 2007 at 09:11:16PM -0400, Bob Rossi wrote:
> > > On Mon, Jun 04, 2007 at 09:08:27AM -0400, Bob Rossi wrote:
> > > > Hi All,
> >
On Mon, Jun 11, 2007 at 09:11:16PM -0400, Bob Rossi wrote:
> On Mon, Jun 04, 2007 at 09:08:27AM -0400, Bob Rossi wrote:
> > Hi All,
> >
> > I think it's about time we finish up the push parser. I've become very
> > busy lately and don't have a lot of tim
On Mon, Jun 04, 2007 at 09:08:27AM -0400, Bob Rossi wrote:
> Hi All,
>
> I think it's about time we finish up the push parser. I've become very
> busy lately and don't have a lot of time. What would be required of me
> to get push.c moved over to yacc.c?
>
>
Hi All,
I think it's about time we finish up the push parser. I've become very
busy lately and don't have a lot of time. What would be required of me
to get push.c moved over to yacc.c?
I'd like to make sure this gets into the next release as I'll need it
for
On Tue, Feb 27, 2007 at 07:20:31PM +0100, Hans Aberg wrote:
> On 27 Feb 2007, at 16:51, Bob Rossi wrote:
>
> >I'm using bison along with it's semantic actions. In particular, I'm
> >using the $$, $1, $2 constructs in order to help me build a parse
> >tree.
On Tue, Feb 27, 2007 at 04:15:39PM -0500, Joel E. Denny wrote:
> On Tue, 27 Feb 2007, Bob Rossi wrote:
>
> > However, I'm wondering if it's possible, after the parse is done, to ask
> > bison to give you back the top level's rule $$ variable. That way, I
>
l variable.
However, I'm wondering if it's possible, after the parse is done, to ask
bison to give you back the top level's rule $$ variable. That way, I
don't have to keep around an extra global variable.
Is this question clear e
On Mon, Feb 26, 2007 at 12:19:18AM +0100, Hans Aberg wrote:
> On 25 Feb 2007, at 19:47, Bob Rossi wrote:
> >I see the problem now. I #include OutGrammar.h into Lexer.l.
> >OutGrammar.h has the C++ type (std::string) information in it.
> >
> >This causes a compile erro
On Sat, Feb 24, 2007 at 01:49:26PM -0500, Joel E. Denny wrote:
> On Sat, 24 Feb 2007, Bob Rossi wrote:
>
> > How come if I do
> >
> > %union {
> > std::string *foo;
> > }
> >
> > I get,
> > error: expected specifier-qualifier-list
come if I do
%union {
std::string *foo;
}
I get,
error: expected specifier-qualifier-list before ‘std’
I found a work around, which is to do
struct s {
std::string foo;
};
%union {
struct s *foo;
};
Do I have to do it this way? Is there a better work around?
Thanks,
depend on much of
the C library.
Now, if you want to compile bison for windows, you can use the mingw
port of gcc. Others have built bison using this port. Here is some
information on this subject.
http://www.mingw.org/MinGWiki/index.php/bison?PHPSESSID=e7de1a0bfb50812a5b49513a95344d14
I'm n
e trying to run it.
Yes it does. For windows look at mingw port, you can download a binary.
Otherwise, bison ports to all major unix systems.
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On Wed, Dec 13, 2006 at 05:11:37PM -0500, Joel E. Denny wrote:
> On Wed, 13 Dec 2006, Bob Rossi wrote:
>
> > $ m4 --version
> > GNU M4 1.4.8
> > [EMAIL PROTECTED] ~/cvs/bison/original/bison
> > $ autoconf --version
> > autoconf (GNU Autoconf) 2.61
>
On Wed, Dec 13, 2006 at 04:57:33PM -0500, Bob Rossi wrote:
> On Wed, Dec 13, 2006 at 04:23:29PM -0500, Joel E. Denny wrote:
> > On Wed, 13 Dec 2006, Joel E. Denny wrote:
> >
> > > On Wed, 13 Dec 2006, Bob Rossi wrote:
> > >
> > > > With a fresh ch
On Wed, Dec 13, 2006 at 04:23:29PM -0500, Joel E. Denny wrote:
> On Wed, 13 Dec 2006, Joel E. Denny wrote:
>
> > On Wed, 13 Dec 2006, Bob Rossi wrote:
> >
> > > With a fresh check out, and autoconf 2.6.1 on my path, after running
> > > ./bootstrap.sh
&g
On Wed, Dec 13, 2006 at 04:03:31PM -0500, Joel E. Denny wrote:
> On Wed, 13 Dec 2006, Bob Rossi wrote:
>
> > With a fresh check out, and autoconf 2.6.1 on my path, after running
> > ./bootstrap.sh
>
> You mean "./bootstrap", right?
Yes.
> I just tried
On Wed, Dec 13, 2006 at 03:28:29PM -0500, Joel E. Denny wrote:
> On Wed, 13 Dec 2006, Bob Rossi wrote:
>
> > > 2.61 has some corrections regarding strange test case titles, which my
> > > recent patches add to Bison. I can't promise it'll fix your problem
On Wed, Dec 13, 2006 at 03:21:25PM -0500, Joel E. Denny wrote:
> On Wed, 13 Dec 2006, Bob Rossi wrote:
>
> > On Wed, Dec 13, 2006 at 03:13:30PM -0500, Joel E. Denny wrote:
> > > On Wed, 13 Dec 2006, Bob Rossi wrote:
> > >
> > > > m
On Wed, Dec 13, 2006 at 03:13:30PM -0500, Joel E. Denny wrote:
> On Wed, 13 Dec 2006, Bob Rossi wrote:
>
> > make maintainer-check recently broke in CVS.
> >
> > $ make maintainer-check
> > cd tests && make maintainer-check
> > make[1]: Entering direc
ax error near unexpected token `('
./testsuite: line 657: `44;output.at:190;Output file name: (;c++;'
make[1]: *** [maintainer-check-posix] Error 2
make[1]: Leaving directory `/home/bob/cvs/bison/round2/bison/tests'
make: *** [maintainer-check] Error
ork or
> it's normal?
>
> Why do I dont have a new .c file.
> Here is the command I ran: bison -d -l -S yyparse.c -o tcyacc.c TL1.y
I'm not sure. Maybe someone else will know. This is the command I use.
bison -S push.c -l gdbmi_grammar.y
Bob Rossi
__
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
How do you run a single test case in the test suite?
Thanks,
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
, report early, report often.
Anyways, as you see problems, and report them, they can be fixed if they
are bugs. Others will benefit from your frustrations.
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On Wed, Oct 11, 2006 at 10:28:58PM +0200, Hans Aberg wrote:
> On 11 Oct 2006, at 22:27, Bob Rossi wrote:
>
> >>You must make sure M4 is installed - Bison uses it for generating
> >>files.
> >
> >OK, I didn't uninstall it, and I've been doing this al
On Wed, Oct 11, 2006 at 10:24:40PM +0200, Hans Aberg wrote:
On 11 Oct 2006, at 22:20, Bob Rossi wrote:
Now when I run my push parser out of CVS I get this:
$ bison -S push.c -l gdbmi_grammar.y
/usr/bin/m4: /home/bob/cvs/bison/bison/bison/../prefixdir/share/
bison/bison.m4: No such file or
/share/bison/
c.m4glr.c lalr1.cc m4sugar README
c++.m4 glr.cc location.cc push.c yacc.c
Have I done something wrong? or was something recently broken in CVS?
Thanks,
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help
erated parser. This should
point you to the problem.
Bob Rossi
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
ange code of bison 1.875 and flex 2.5.4a
> to make a reentrant parser ?
Hi Philippe,
You can most likely get a bison parser for windows that honors the
reentrant options, however, have you considered generating the parser
from linux and using the gen
yyparse through to yylex. */
> #define YYPARSE_PARAM scanner
> #define YYLEX_PARAM scanner
> #include
> %}
> %locations
> %pure_parser
You want %pure-parser.
Bob Rossi
___
Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
Hi,
What's the difference between yacc.c or glr.c? I'm specifically asking
because I would like to understand where I should begin with my push
parser effort.
Thanks,
Bob Rossi
___
Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
OK, The subject here is inappropriate. Maybe this will help things.
Bob Rossi
On Tue, Jan 31, 2006 at 10:52:13AM -0500, Bob Rossi wrote:
> On Thu, Jan 19, 2006 at 10:18:42PM +0100, Odd Arild Olsen wrote:
> > The copyright transfer of my Bison extensions are now complete.
>
> Gre
provides?
I'm going to take a closer look at what Odd has done now, so I can get a
better understanding of the task ahead.
Thanks,
Bob Rossi
___
Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On Thu, Dec 22, 2005 at 08:18:40PM -0500, Bob Rossi wrote:
> On Wed, Dec 21, 2005 at 09:06:06AM +0100, Akim Demaille wrote:
> > >>> "Odd" == Odd Arild Olsen <[EMAIL PROTECTED]> writes:
> >
> > Hi Odd,
> >
> > > I would be
h the FSF?
Odd has already stated this:
I have no problem with any opens source license, and I can
register with and transfer copyright to FSF any day. I would be happy to see
anyone bring the patch into Bison.
On Wed, Dec 21, 2005 at 06:37:03PM -0500, [EMAIL PROTECTED] wrote:
> Hello Folks:
>
> I would like to cease getting E-mails, but I haven't found an obvious way to
> get off. Please advise.
Go to http://lists.gnu.org/mailman/listinfo/help-bison/ and use the
"Unsubscri
tion over and over. Or would there simply
have to be 2 skeleton's released, so that if you want asynchronous
functionality out of bison you have to do --skeleton= option?
Thanks,
Bob Rossi
___
Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
n bison. I will spend
some time looking at this. Is there anything in particular which
prevented it from being included into bison?
Thanks,
Bob Rossi
___
Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On Mon, Dec 19, 2005 at 05:09:31PM +0100, Akim Demaille wrote:
> >>> "Bob" == Bob Rossi <[EMAIL PROTECTED]> writes:
>
> > Well, who would I talk to about modifying bison to be used in an
> > asynchronous manner? I found this Email from 2002
> &g
On Mon, Dec 19, 2005 at 06:50:05AM +0100, Hans Aberg wrote:
>
> On 16 Dec 2005, at 02:04, Bob Rossi wrote:
>
> >Am I correct in assuming that both flex and bison are unmaintained? or
> >is there an active community working on these projects?
>
> For Flex:
>
On Thu, Dec 15, 2005 at 10:31:29PM -0500, Joel E. Denny wrote:
> On Thu, 15 Dec 2005, Bob Rossi wrote:
>
> > Am I correct in assuming that both flex and bison are unmaintained? or
> > is there an active community working on these projects?
>
> Bison is certainly maintain
amount of work.
Bob Rossi
___
Help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On Thu, Dec 15, 2005 at 02:08:04AM +0100, Michael Brandt wrote:
> On 15/12/05, Bob Rossi <[EMAIL PROTECTED]> wrote:
> > > The lemon parser generator uses "inverted flow-of-control", the
> > > user/lexer calls the parser for each input token.
> >
On Thu, Dec 15, 2005 at 12:16:07AM +0100, Michael Brandt wrote:
> On 14/12/05, Bob Rossi <[EMAIL PROTECTED]> wrote:
> > Does bison currently support "inverted flow-of-control"? Do you
> > recommend another package for this? Could I come up with some patches
>
On Wed, Dec 14, 2005 at 05:22:29PM +1100, Russell Shaw wrote:
> Bob Rossi wrote:
> >Hi All,
> >
> >I'm writing a GPL'd ncurses front end to GDB, called CGDB.
>
> Did you know gdb already has a curses frontend?
>
> gdb -tui
In particular, according to
On Wed, Dec 14, 2005 at 05:22:29PM +1100, Russell Shaw wrote:
> Bob Rossi wrote:
> >Hi All,
> >
> >I'm writing a GPL'd ncurses front end to GDB, called CGDB.
>
> Did you know gdb already has a curses frontend?
>
> gdb -tui
Yeah, I do. I have several
l design that people are aware of that will allow me
to basically pass data to bison as I get it? or do I have to have the
entire response from GDB before I can invoke the bison parser in order
to keep the design of CGDB reasonable simple?
Any advice would be greatly a
72 matches
Mail list logo
