From: skaller <skaller@users.sourceforge.net>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocamlyacc -- can i tell it to be quiet?
Date: Sat, 19 Nov 2005 01:22:33 +1100 [thread overview]
Message-ID: <1132323753.10869.34.camel@rosella> (raw)
In-Reply-To: <1132322923.10869.29.camel@rosella>
On Sat, 2005-11-19 at 01:08 +1100, skaller wrote:
> The following leads to shift reduce conflict:
>
> ctype_name:
> | LONG LONG
> | LONG
>
> Yacc is very weird -- I can parse a list of LONG without
> a conflict .. but not two of them??
Oopps, sorry, another case of find the bug immediately after
posting .. lol .. the conflict is not in the above productions,
but only in combination with another production
which is effectively:
name: ctype_name
application:
| name name
| name
so of course there is a real conflict ..
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2005-11-18 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 14:08 skaller
2005-11-18 14:16 ` [Caml-list] " Sebastian Egner
2005-11-18 15:59 ` skaller
2005-11-18 14:22 ` skaller [this message]
2005-11-18 14:34 ` Jon Harrop
2005-11-18 14:58 ` Christian Lindig
2005-11-18 14:40 yoann padioleau
2005-11-18 16:25 ` skaller
2005-11-18 16:34 yoann padioleau
2005-11-18 17:56 ` skaller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1132323753.10869.34.camel@rosella \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).