Hi John,
> Le 28 nov. 2020 à 11:27, John P. Hartmann a écrit :
>
> His goof was to specify '=' (three characters) in flex. So the = token never
> got to the parser.
Doh... I didn't see it :(
Thanks for the resolution of the mystery :)
His goof was to specify '=' (three characters) in flex. So the = token
never got to the parser.
On 11/28/20 09:49, Akim Demaille wrote:
Hi Jot,
Le 27 nov. 2020 à 11:20, Jot Dot a écrit :
What do you mean? It did display "go to state 31", but did not? Could you
please provide us with the
Hi Jot,
> Le 27 nov. 2020 à 11:20, Jot Dot a écrit :
>
>> What do you mean? It did display "go to state 31", but did not? Could you
>> please provide us with the full trace? Also, have you tried to enable the
>> Flex traces, just in case.
>
> My input string is "CONST\n\trange = 1..10;\n"
>
On Freitag, 27. November 2020 14:22:29 CET Jot Dot wrote:
> Thanks for everyone's help. Problem is resolved.
> I was asking Akim about what he said: FWIW, I prefer to explicitly
> "continue;" in these cases."If you have a moment of time Akim, can you
> explain? If not, I can do some googling on thi
e along my way.
- Original Message -
From: Christian Schoenebeck
To: help-bison@gnu.org
Cc: Jot Dot , Akim Demaille
Sent: Fri, 27 Nov 2020 04:27:39 -0700 (MST)
Subject: Re: confusing bison error
On Freitag, 27. November 2020 11:20:29 CET Jot Dot wrote:
> I learned to distrust Flex's
On Freitag, 27. November 2020 11:20:29 CET Jot Dot wrote:
> I learned to distrust Flex's handling of comments when they are in column 0.
>
> Yea, I'm starting to notice "something is up" with the first column.
Like Akim pointed out, you should never place comments on the first column in
Flex's r
quot;+"/" { if (comment_nesting) --comment_nesting;
else BEGIN(INITIAL); }
"*"+ ; /* Line 11 */
[^/*\n]+ ; /* Line 12 */
[/] ; /* Line 13 */
\n ; /* Line 14 */
}
From: "Akim Demaille"
To: "Jot Dot"
Cc: help-bison@gnu.org
Sent: Friday, No
Hi Jot,
> Le 27 nov. 2020 à 01:11, Jot Dot a écrit :
>
> FWIW: I'm new to flex/bison (lex/yacc) but I understand the basic concepts.
> win_flex 2.6.4
> bison (GNU Bison) 3.7.1
I'd prefer that you use the most recent release, although it shouldn't make any
difference here.
> Having said tha
FWIW: I'm new to flex/bison (lex/yacc) but I understand the basic concepts.
win_flex 2.6.4
bison (GNU Bison) 3.7.1
I am hoping someone can point me in the right direction. I hope I have a
setting wrong or missed something simple.
I want to use ordinary symbols in rules for my .y file such as
Le 27 janv. 2013 à 00:45, Bernd Clausen a écrit :
> I have the following destructor specified for strings like IDENT.
>
> %destructor { printf ("free at line %d: %s\n",@$.first_line, $$->c_str());
> delete($$); }
>
> Now I have the following input. The first line is valid, the second line
>
I have the following destructor specified for strings like IDENT.
%destructor { printf ("free at line %d: %s\n",@$.first_line, $$->c_str());
delete($$); }
Now I have the following input. The first line is valid, the second line isn't
(identifier is missing):
ConfigParam p;
ConfigPara
On 12 Dec 2008, at 15:14, sgaurelius wrote:
So, you re saying to do the first and add more errors as I find
more errors.
Yeah, I guess this is the optimal.
Since it goes deep until finding the first error, it will print
messages for
all errors or for the most basic one ? The latter is bett
Using LR(1) without such state compaction having that
> flaw might be better.
>
>Hans
>
>
>
>
> ___
> help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
>
>
--
View this message in context:
http://www.nabble.com/Bison-error-handling-tp20964993p20976407.html
Sent from the Gnu - Bison - Help mailing list archive at Nabble.com.
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
On 12 Dec 2008, at 00:39, sgaurelius wrote:
if I want to define, exactly what messages or actions bison should
do when
an error occurs, what should I do. From what I 've searched, either
I can do
1) what is says in
http://www.slac.stanford.edu/comp/unix/gnu-info/bison_9.html
or
2) what is s
context:
http://www.nabble.com/Bison-error-handling-tp20964993p20964993.html
Sent from the Gnu - Bison - Help mailing list archive at Nabble.com.
___
help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
> > When i run my parser on a VRML 2.0 file
> > or the DIVE VRML 1.0 parser on a VRML 1.0 file,
> > i get the following error, which is not too
> > informative:
> >
> > redblue.wrl:5: Error:
> > syntax error before '?'
> >
> > How can i get these error messages more informative,
> > for example ho
On 12 Apr 2007, at 15:54, Tamas Nagy wrote:
When i run my parser on a VRML 2.0 file
or the DIVE VRML 1.0 parser on a VRML 1.0 file,
i get the following error, which is not too
informative:
redblue.wrl:5: Error:
syntax error before 'å'
How can i get these error messages more informative,
for e
Hi!
When i run my parser on a VRML 2.0 file
or the DIVE VRML 1.0 parser on a VRML 1.0 file,
i get the following error, which is not too
informative:
redblue.wrl:5: Error:
syntax error before 'å'
How can i get these error messages more informative,
for example how to print the last good token?
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 all along.
> >Something
> >else must have gone
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 all along.
Something
else must have gone wrong?
$ which m4
/usr/bin/m4
Dunno - maybe a bug then.
Hans Aberg
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 dire
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 directory
And
[EMAIL PROTECTED] ~/download/gdbmi
$ ls /home/b
Hi,
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 directory
And
[EMAIL PROTECTED] ~/download/gdbmi
$ ls /home/bob/cvs/bison/bison/bison/../prefixdir/share
23 matches
Mail list logo
