On 12/20/19, David Given wrote:
> Does anyone know if the original source code for the lemon parser still
> exists, and if so, where to find it?
>
> The lemon.c file shipped with sqlite, which the hwaci website points me at,
> does not appear to be it --- instead it's an amalgamation of a bunch
On 8/31/18, Warren Young wrote:
> They’re separate. Here’s the Tcl source for the bubble diagrams:
>
> https://www.sqlite.org/docsrc/file/?name=art/syntax/bubble-generator-data.tcl
>
> …and here’s the Lemon grammar for SQLite’s SQL parser:
>
> https://www.sqlite.org/src/file?name=src/parse.y
On Fri, Aug 31, 2018 at 2:59 PM Warren Young wrote:
>
> On Aug 31, 2018, at 1:55 PM, Scott Robison wrote:
> >
> > Is one generated from the other, or are they maintained separately?
>
> They’re separate. Here’s the Tcl source for the bubble diagrams:
As I suspected having looked at them in the
On Aug 31, 2018, at 1:55 PM, Scott Robison wrote:
>
> Is one generated from the other, or are they maintained separately?
They’re separate. Here’s the Tcl source for the bubble diagrams:
https://www.sqlite.org/docsrc/file/?name=art/syntax/bubble-generator-data.tcl
…and here’s the Lemon
On 4/25/17, Kelvin Sherlock wrote:
>
> I believe the issue is line 4164 which should be … = LEMON_TRUE. Currently,
> when i=0, all rules will erroneously be optimized out.
>
> 4157/* Mark rules that are actually used for reduce actions after all
> 4158**
On 10/8/16, Conor O'Rourke wrote:
> I believe the Lemon documentation at:
> http://www.hwaci.com/sw/lemon/lemon.html is out of date with respect to the
> default token type. If I create a parser with no token_type override, the
> default type is:
>
> #define
On 8/16/16, xiaobing wrote:
> In lemon.c:ReportTable() , when " Combine duplicate destructors into a
> single case ", sp2->destructor is set to 0, but later it is used in
> tranlate_code to generate destructor.
> so if you have grammar like this:
> %destructor expr_a {
On 12/07/2016 22:01, Richard Hipp wrote:
OK. Another fix. Please try the latest trunk version.
This version works for me. Thanks.
Nick
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
On 7/9/16, Nick Wellnhofer wrote:
>
> This still doesn't work for me.
OK. Another fix. Please try the latest trunk version.
Note to passive readers of this thread: none of this has any impact on
SQLite. SQLite does not use the feature of the Lemon LALR(1) parser
On 08/07/2016 21:54, Richard Hipp wrote:
Please try again with the latest version of Lemon. Thanks.
This still doesn't work for me. I created a GitHub repo to demonstrate the
problem:
https://github.com/nwellnhof/lemon-bug
Nick
___
On 08/07/2016 21:54, Richard Hipp wrote:
Please try again with the latest version of Lemon. Thanks.
On 7/6/16, Nick Wellnhofer wrote:
On 05/07/2016 18:12, Richard Hipp wrote:
Please try https://www.sqlite.org/src/info/2683b375ad129117 and verify
that the changes on
Please try again with the latest version of Lemon. Thanks.
On 7/6/16, Nick Wellnhofer wrote:
> On 05/07/2016 18:12, Richard Hipp wrote:
>> Please try https://www.sqlite.org/src/info/2683b375ad129117 and verify
>> that the changes on trunk are working. Thanks.
>
> Still
On 05/07/2016 18:12, Richard Hipp wrote:
Please try https://www.sqlite.org/src/info/2683b375ad129117 and verify
that the changes on trunk are working. Thanks.
Still doesn't work for me. The structure of the #ifdefs in `Parse` is:
#ifdef YYERRORSYMBOL
...
#elif
Please try https://www.sqlite.org/src/info/2683b375ad129117 and verify
that the changes on trunk are working. Thanks.
On 7/5/16, Nick Wellnhofer wrote:
> On 05/07/2016 17:15, Richard Hipp wrote:
>> On 7/5/16, Nick Wellnhofer wrote:
>>> No, this doesn't
On 05/07/2016 17:15, Richard Hipp wrote:
On 7/5/16, Nick Wellnhofer wrote:
No, this doesn't fix my problem. The check-in only changes the "#ifdef
YYERRORSYMBOL" branch which I don't define. But if I add the change to the
"YYERRORSYMBOL is not defined" branch as well,
On 7/5/16, Nick Wellnhofer wrote:
> No, this doesn't fix my problem. The check-in only changes the "#ifdef
> YYERRORSYMBOL" branch which I don't define. But if I add the change to the
> "YYERRORSYMBOL is not defined" branch as well, everything works as
> expected.
Can you
No, this doesn't fix my problem. The check-in only changes the "#ifdef
YYERRORSYMBOL" branch which I don't define. But if I add the change to the
"YYERRORSYMBOL is not defined" branch as well, everything works as expected.
Thanks for the quick response!
Nick
On 05/07/2016 14:48, Richard Hipp
Please try the latest check-in
(https://www.sqlite.org/src/info/91889fa30e84760e) and let me know
whether or not it clears your problem.
On 7/5/16, Nick Wellnhofer wrote:
> Hello,
>
> I hope this is right place to report Lemon issues. I ran into a problem
> after
> upgrading
On Fri, Jun 17, 2016 at 11:50:48AM -0400, Richard Hipp wrote:
> On 6/6/16, Vincent Zweije wrote:
>
> >
> > When the shiftreduce action is used in an error context,
> > such as:
> >
> >X -> alpha error.
> >
> > the adjustment is not made. This causes error handling to
On 6/6/16, Vincent Zweije wrote:
>
> When the shiftreduce action is used in an error context,
> such as:
>
>X -> alpha error.
>
> the adjustment is not made. This causes error handling to fail.
>
Is this problem fixed by
Hello,
Le samedi 26 juillet 2014, Richard Hipp a écrit :
>
> Historical note: I wrote Lemon back in the 80s (on a Sun3, IIRC)
You were a visionary, Lemon is probably the only viable option for a parser
generator in C/C++ at this moment.
because
> the $1,$2,$3 notation of
On Sat, Jul 26, 2014 at 11:10 AM, Sylvain Pointeau <
sylvain.point...@gmail.com> wrote:
> Hello,
>
> I would like to know if %wildcard is an undocumented feature on purpose, is
> this safe to use it?
>
Historical note: I wrote Lemon back in the 80s (on a Sun3, IIRC) because
the $1,$2,$3
I see; well, that's unfortunate. At any rate, parsing lempar.c will
probably be much more complex than the code I have now, which solves a
simple (but common) case. Maybe I'll look into parsing lempar.c, but since
this solves my use case, I probably won't be in a hurry to do it. I
apologise to
On Mon, Jan 7, 2013 at 4:18 PM, Tiago Rodrigues wrote:
> Oops, Dominique alerted me to the fact that the patch I included was
> stripped by the listserver... I'm including it inline, then.
>
This patch does not work in the general case. I don't doubt that it works
for your
Oops, Dominique alerted me to the fact that the patch I included was
stripped by the listserver... I'm including it inline, then.
(Begin patch)
--- lemon.c2013-01-04 20:39:20 +
+++ lemon-new.c2013-01-04 23:09:59 +
@@ -109,7 +109,7 @@
void Reprint(struct lemon *);
void
On 18 Oct 2012, at 20:07, Richard Hipp wrote:
> On Thu, Oct 18, 2012 at 3:03 PM, Ben wrote:
>
>> Hi list,
>>
>> I'm having a little trouble getting my head around memory management
>> within a Lemon-generated parser. Specifically the part of the
On Thu, Oct 18, 2012 at 3:03 PM, Ben wrote:
> Hi list,
>
> I'm having a little trouble getting my head around memory management
> within a Lemon-generated parser. Specifically the part of the docs stating
> when a destructor will or will not be called.
>
> For example,
On Sat, Jan 07, 2012 at 10:18:12AM -0500, Richard Hipp wrote:
|| On Wed, Jan 4, 2012 at 11:00 AM, Vincent Zweije wrote:
||
|| > I may have hit a bug in the lemon parser generator.
|| >
||
|| Please see if the following fix clears your problem:
||
||
On Wed, Jan 4, 2012 at 11:00 AM, Vincent Zweije wrote:
> I may have hit a bug in the lemon parser generator.
>
Please see if the following fix clears your problem:
http://www.sqlite.org/src/info/ce32775b23
>
> It looks like lookahead symbols aren't propagated
On Tue, Dec 07, 2010 at 08:09:53PM +0100, Begelman, Jamie wrote:
> I'm using Lemon for a non-sqlite related project and it is exiting with an
> assertion failure that I would like to understand. I have extracted the
> following small set of productions from a larger grammar. The "list"
>
On Tue, Oct 12, 2010 at 6:54 PM, Vincent Adam Burns wrote:
> Is there an active maintainer for the Lemon Parser? I'm getting some
> parsing conflicts, ex:
>
> statement ::= IF LEFT_PAREN expression RIGHT_PAREN statement ELSE
> statement.
> statement ::= IF LEFT_PAREN
On Tue, Apr 6, 2010 at 10:40 PM, Dan Kennedy wrote:
>
> On Apr 7, 2010, at 3:23 AM, Chris verBurg wrote:
>
> > Hehe, okay, here I go. :)
> >
> >
> > I'm trying to replace an existing flex/bison parser with an re2c/lemon
> > parser, but I'm running into a methodological
On Apr 7, 2010, at 3:23 AM, Chris verBurg wrote:
> Hehe, okay, here I go. :)
>
>
> I'm trying to replace an existing flex/bison parser with an re2c/lemon
> parser, but I'm running into a methodological problem. I have a
> hypothetical grammar like this:
>
> file ::= FOO str .
> file ::= BAR
Hehe, okay, here I go. :)
I'm trying to replace an existing flex/bison parser with an re2c/lemon
parser, but I'm running into a methodological problem. I have a
hypothetical grammar like this:
file ::= FOO str .
file ::= BAR str .
Where my keywords are FOO and BAR, and str is any ol'
> I'm using the Lemon parser and running into a methodological problem
that
> I
> wanted to ask the user base about. Is there a mailing list or forum
> specifically for Lemon, or is this it? :)
>
> Thanks,
> -Chris
There is no mailing list specifically for lemon. Some of us are
familiar to
On Dec 22, 2009, at 6:06 PM, Benjamin Peterson wrote:
> I'm using lemon to write a parser for a little language I'm writing.
> I'm wondering how I indicate to lemon that an error has occurred in
> processing and an exit is needed. For example, if I have:
>
> stmt(A) ::= NAME(B). { A =
9 12:54 PM
To: Wilson, Ron P
Cc: General Discussion of SQLite Database
Subject: Re: [sqlite] Lemon parser : compile error when using
"%token_destructor" directive
On Mon, Jun 15, 2009 at 11:42:26AM -0400, Wilson, Ron P wrote:
|| It has been a while since I used lemon (big fan thoug
On Mon, Jun 15, 2009 at 11:42:26AM -0400, Wilson, Ron P wrote:
|| It has been a while since I used lemon (big fan though). Did you resolve
|| this issue or do you still need help?
[It appears my previous response did not get through.]
Looks suspiciously like this problem, which was fixed in
It has been a while since I used lemon (big fan though). Did you resolve this
issue or do you still need help?
RW
Ron Wilson, Engineering Project Lead, 434.455.6453
HARRIS CORPORATION | RF Communications Division
assuredcommunications(tm)
-Original Message-
From:
Greetings,
> Lemon does not have any feature that will provide the application with
> access to the follow-set. You could perhaps tease that informatino
> out of the "*.out" output file using a script, though.
Capital idea! That does indeed do the trick. It's straightforward to
extract the
On Aug 17, 2008, at 1:48 PM, Markus Thiele wrote:
> Greetings,
>
> I've been using Lemon for a small custom compiler project. I've used
> Bison before, and I very much prefer the way Lemon does things,
> there's
> just one feature I'm missing and haven't been able to find.
>
> Bison generates
Hi Arjen,
Thanks for the mail...I found it very helpful and i started to execute
it..I succeeded in doing it...
However i started writing a sample program for converting "Infix to
Prefix"...I am struck at this point ...so can u help me in
writing this program...
Thanks in advance
> Hi,
> Can u send me any documentation on LEMON that u have worked out.
> I have some queries also.
> 1.Does LEMON work on Windows environment?
> 2.I tried but it is not.I heard that it works on Linux environment.I am
> trying to know why not on windows...can u give me some info about it
>
>
arjunkumar keerti wrote:
>Hi,
>I found in wikipedia that Lemon parser is a part of SQLite project but i
>couldn't found any sort of information regarding to LEMON.
>Can u give me any documentation regarding how to install it and how to work
>for some programs on Lemon parser generator or any
Joe Wilson <[EMAIL PROTECTED]> wrote:
>The following grammar may be clearer to you:
Yes, it is many thanks! I believe I am making progress! At least I can see the
picture much clearer now and was able to come up with the following grammar
with just one conflict unsolved:
%left NEWLINE.
--- Ralf Junker <[EMAIL PROTECTED]> wrote:
> > paragraph ::= PARA text.
>
> I observed the new PARA terminal token (the clear separator!?). Unfortunately
> the lexer does not
> generate such a token. Paragraph repeats are also removed.
It was just an HTML-like example. I just wanted to
Many thanks, Joe,
>Your grammar is ambiguous. The text tokens run together for
>various rules because the grammar lacks clear separators between
>them.
OK, I begin to understand. The "clear separators" need to be TERMINALs, right?
I believed that these were imlicit because there are TEXT and
--- Ralf Junker <[EMAIL PROTECTED]> wrote:
> article ::= blocks.
>
> blocks ::= block.
> blocks ::= blocks block.
>
> block ::= heading.
> block ::= paragraph.
>
> heading ::= HEADING_START text HEADING_END.
> heading ::= HEADING_START text.
> heading ::= HEADING_START.
>
> paragraph ::= text
Hello,
I finally find the bug. In fact that was many bugs.
- Grammar rule order.
- Input string not reseted properly.
Thank you.
David
On Nov 18, 2007 10:30 AM, Joe Wilson <[EMAIL PROTECTED]> wrote:
> It's most likely your bug. Just add some debug prints in your grammar
> and tokenizer to see
It's most likely your bug. Just add some debug prints in your grammar
and tokenizer to see what's going on.
See also: ParseTrace() in http://www.hwaci.com/sw/lemon/lemon.html
--- Téragone <[EMAIL PROTECTED]> wrote:
> I have a problem with a rule of a small calculator which accept variables :
>
For those reading this thread, I could solve my problme by using ragel
(http://www.cs.queensu.ca/~thurston/ragel/). You can define leaving
actions but also 'any change' actions. It was also easier to include
in a C++ project then lemon/flex. If my grammar becomes more
complicated, I heard it is
> I do not understand why lemon waits for one more token when it has
> enough information to reduce
...
>
> >>> I don't think you can. Why do you want to? Why not just go
> >>> ahead and send it the next token?
> >>>
> >> Most people find a way around this problem using
Gaspard Bucher wrote:
> PS: There is another reason, aside from aesthetics and simpler grammar
> to filter white spaces inside the tokenizer: you avoid all the parser
> conflicts you could get with "empty | or space" rules.
>
> 2007/10/24, Gaspard Bucher <[EMAIL PROTECTED]>:
>
>>> Gaspard
PS: There is another reason, aside from aesthetics and simpler grammar
to filter white spaces inside the tokenizer: you avoid all the parser
conflicts you could get with "empty | or space" rules.
2007/10/24, Gaspard Bucher <[EMAIL PROTECTED]>:
> > Gaspard Bucher <[EMAIL PROTECTED]> wrote:
> > > I
> Gaspard Bucher <[EMAIL PROTECTED]> wrote:
> > I do not understand why lemon waits for one more token when it has
> > enough information to reduce.
> >
> > I want to recognize :
> > foo = Bar()
> > when the token CLOSE_PAR is received, not when an extra token is parsed..
> >
> > How can I avoid
Gaspard Bucher <[EMAIL PROTECTED]> wrote:
> I do not understand why lemon waits for one more token when it has
> enough information to reduce.
>
> I want to recognize :
> foo = Bar()
> when the token CLOSE_PAR is received, not when an extra token is parsed.
>
> How can I avoid lemon waiting for
Richard,
this helped me greatly! I also derived from your example that I can use
multiple characters without conflicts like this:
---
doc ::= inline_list.
// List of allowed characters. Add more as you like.
c ::= CHAR.
c ::= SPACE.
// The c character repeat.
chars ::= c.
chars
Richard,
this helped me greatly! I also derived from your example that I can use
multiple characters without conflicts like this:
---
doc ::= inline_list.
// List of allowed characters. Add more as you like.
c ::= CHAR.
c ::= SPACE.
// The c character repeat.
chars ::= c.
chars
Ralf Junker <[EMAIL PROTECTED]> wrote:
> I am writing to ask for help about how to solve The Lemon parser conflicts.
>
> As part of a larger grammar, I am need to implement this regular expression
> in Lemon:
>
> (.+|'.+')+
>
> I tried lots of grammars, but all of them generated Lemon
Uma Krishnan uttered:
Hey, There's no need to be offensive. I did not mean to be critical. Far
from it, it does a great a job (far more than I'm capable of producing).
What I was trying to find out was, if it is possible for a .y files to
be broken such that it can be built on top on other .y
Hey, There's no need to be offensive. I did not mean to be critical. Far from
it, it does a great a job (far more than I'm capable of producing). What I was
trying to find out was, if it is possible for a .y files to be broken such that
it can be built on top on other .y files.
Not sure
Uma Krishnan uttered:
Hello:
Is lemon parser modular and extensible?
Extensible to do what? It generates parsers, and is self contained. It
does a single job, and does it well. What more could you ask for?
Thanks
Uma
Asif Lodhi <[EMAIL PROTECTED]> wrote:
Hi Everybody,
I have
Thanks again Ulrik...the problem was with the tokenizer and not the
parser...
Medi
-Original Message-
From: Medi Montaseri [mailto:[EMAIL PROTECTED]
Sent: Friday, May 04, 2007 5:14 PM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Lemon parser generator question
Thanks Ulrik...I am
Thanks Ulrik...I am now looking for the lexer...
Medi
-Original Message-
From: Ulrik Petersen [mailto:[EMAIL PROTECTED]
Sent: Friday, May 04, 2007 4:30 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Lemon parser generator question
Medi,
Lemon is a parser, not a lexer
Medi,
Lemon is a parser, not a lexer. The terminals are defined outside of
Lemon. Perhaps you inherited the .y file but did not receive the
lexer/tokenizer?
SQLite, for example, has a hand-coded tokenizer. Other projects (such
as my own) may use a lexer-generator such as flex.
In
[EMAIL PROTECTED] wrote:
>
> then I use the command
>
> lemon parse.y
>
> I successfully get the parse.h file
>
> but the file is not right.
> I only get 137 ids
>
> the follwing 15 ids do not exist in the parse.h
>
> TK_TO_TEXT
>
> TK_CONST_FUNC
>
You need to run the awk script
Cesar Rodas wrote:
The URL is ok, I opened here...
Works fine in .uk too
Martin
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
URL didn't work for me either, but you'll see what you want at the root
(at least today):
http://www.cesarodas.com/
-Original Message-
From: Cesar Rodas [mailto:[EMAIL PROTECTED]
Sent: Monday, March 05, 2007 10:44 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Lemon example
The URL is ok, I opened here... try again and let me know if you could not
and I will email you the content of the example.
On 05/03/07, Clay Dowling <[EMAIL PROTECTED]> wrote:
Cesar Rodas wrote:
> Here is Lemon tutorial. Shows how to make a calculator with a
feature of
> use Parents "()"
Cesar Rodas wrote:
> Here is Lemon tutorial. Shows how to make a calculator with a feature of
> use Parents "()" in math expression.
> http://www.cesarodas.com/2007/03/creating-basic-calculator-with-lemon.html.
>
> The author disclaims the copyright of the calculator.
There's a problem with
[EMAIL PROTECTED] schrieb:
> dear all:
> i am a programmer from China, i use sqlite in my project.
> from sqlite, i know lemon.
> i work on windows, using vc6.0, i am trying to do something using lemon,
> but i have some issues.
> i write a my_calculator.y file, and generate
Original Message-
> From: Cesar Rodas [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 29, 2006 11:17 AM
> To: sqlite-users@sqlite.org; [EMAIL PROTECTED]
> Subject: Re: [sqlite] LEMON
>
> Another URL where i can find a tutorial?
>
> On 29/12/06, Lloyd <[EMAIL PR
, 2006 11:17 AM
To: sqlite-users@sqlite.org; [EMAIL PROTECTED]
Subject: Re: [sqlite] LEMON
Another URL where i can find a tutorial?
On 29/12/06, Lloyd <[EMAIL PROTECTED]> wrote:
>
> Ethereal make use of Lemon
>
> On Fri, 2006-12-29 at 11:08 -0400, Cesar Rodas wrote:
> &g
I'm not familiar with Lemon, so I don't know if this will help:
http://linuxgazette.net/106/chirico.html. Also, I'd highly recommend just
doing a Google search for either "Lemon Parser" or "Lemon Tutorial".
--
Eric Pankoke
Founder / Lead Developer
Point Of Light Software
Clifton Park, New York 12065
518-371-3983 x113 (work)
860-508-5015 (cell)
-Original Message-
From: Cesar Rodas [mailto:[EMAIL PROTECTED]
Sent: Friday, December 29, 2006 11:17 AM
To: sqlite-users@sqlite.org; [EMAIL PROTECTED]
Subject: Re: [sqlite] LEMON
Another URL where i can find a tutorial
Another URL where i can find a tutorial?
On 29/12/06, Lloyd <[EMAIL PROTECTED]> wrote:
Ethereal make use of Lemon
On Fri, 2006-12-29 at 11:08 -0400, Cesar Rodas wrote:
> Where can i find a tutorial with examples of how to use LEMON parser...
> because i need to build interpreted language
>
>
Ethereal make use of Lemon
On Fri, 2006-12-29 at 11:08 -0400, Cesar Rodas wrote:
> Where can i find a tutorial with examples of how to use LEMON parser...
> because i need to build interpreted language
>
> Thanks to all
__
Scanned and protected by Email
Michael Somos wrote:
I found the following for "lemon" in the sqlite-3.3.6 distribution :
===
lemon -x
Lemon version 1.0
lemon /dev/null
Segmentation fault
gdb ./lemon
GNU gdb 6.4
Copyright
Ludvig Strigeus wrote:
With Bison, you can do something like this (not quite bison syntax):
myrule: TYPE IDENT {DoSomethingRightAfterIdent($1,$2); } LP more_rules
RP; {DoSomethingAfterEverything($1,$2,$5); }
I.e. you have a chunk of C code that's called in the middle of the
processing of the
On Thu, Aug 05, 2004 at 09:07:36AM -0400, Joseph Stewart wrote:
> Many thanks for your contribution!
> -joe
>
> On Wed, 4 Aug 2004 22:02:48 -0400, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > A user earlier posted a question about terminating
> > the grammer for a simple calculator done
Many thanks for your contribution!
-joe
On Wed, 4 Aug 2004 22:02:48 -0400, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> A user earlier posted a question about terminating
> the grammer for a simple calculator done with lemon.
>
> I ran into the same problem and had to use
> the following,
I'll second sporkey, would you be able to post your calc source for us
all to see?
TIA,
-j
On Tue, 03 Aug 2004 15:38:53 -0400, John Cohen <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Thanks for all the help! I got it all working fine.. The wrapper did the
> trick - I also want to try some speed
D. Richard Hipp wrote:
John Cohen wrote:
The last suggestion worked great (thanks!). But still, I still have a
small problem. It won't accept more than one 'statement'. I know
why, but can't fix it. Take a look:
$ ./a.out
7 + 9 + 7 + 3 / (5 + 7);
23.25
3 + 3 + 3;
Fatal Error: Parser
On Tue, 2 Aug 2004, John Cohen wrote:
>
>in ::= in stmt ENDLINE.
>
>But that doesn't seem to work in lemon. I've also tried making the 2nd
>statement right recursive, but that doesn't work either because it doesn't
>seem to ever reduce all the way.
>
>Any ideas? Much thanks to all.
Just make
Date: Mon, 02 Aug 2004 23:51:15 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Aha! =)
The last suggestion worked great (thanks!). But still, I still have a small
problem. It won't accept more than one 'statement'. I know why, but can't
fix it. Take a look:
$ ./a.out
7 +
Monday, August 2, 2004, 12:49:50 AM, John Cohen wrote:
> My problem is the fact I cannot use the start token on the right hand of the
> rule. [...]
> How can I get this to accept things such as:
> 5 + 5 + 5
> 5 + 6
> ?
[I have never used lemon, but perhaps something like...]
expr := term |
Sean Chittenden wrote:
Howdy. Having been fed up with bison/yacc, I switched to using lemon
and have found lemon to be a vastly more enjoyable tool to work with
compared to bison (thank you!). That said, before I embarked on my
wholesale conversion to lemon, I went and recreated a calculator
87 matches
Mail list logo