The problem is my bison file having different precedence for '>' '>' than
'>' even though they are right next to eachother its still incorrect to
treat >> the same precedence as >
On Wed, Apr 3, 2013 at 2:28 PM, Hans Aberg wrote:
> On 3 Apr 2013, at 04:52, Adam Smalin wrote:
>
> > ... I have n
Interesting, but than the issue is how do I make > > higher than > and ?:
but lower than *
I think i'm going to go through severe pain. I'm going to keep this last so
i can make all syntax changes at the end and break everything once.
On Wed, Apr 3, 2013 at 12:39 AM, Akim Demaille wrote:
>
> L
On 3 Apr 2013, at 04:52, Adam Smalin wrote:
> ... I have no idea how i can fix this without rewriting it all.
Have you tried getting the lexer to emit two '>' when it sees a ">>", say by
using an parenthesis-matching integer count?
Hans
___
help-
Seems like it would be (more than) helpful if Bison would report
any use of %dprec that will fail to actually affect the resulting parser!
___
help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
