[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bison info doc - precedence in recursive parsing
From: |
Hans Åberg |
Subject: |
Re: bison info doc - precedence in recursive parsing |
Date: |
Mon, 4 Feb 2019 10:52:28 +0100 |
> On 3 Feb 2019, at 07:50, address@hidden wrote:
>
> The first effect of the precedence declarations is to assign precedence
> levels to the terminal symbols declared. The second effect is to assign
> precedence levels to certain rules: each rule gets its precedence from the
> last terminal symbol mentioned in the components.
If you write the .output file using --verbose or %verbose, the precedence makes
a choice at the parsing dot "." in the case of a shift/reduce conflict, see the
Bison manual, sec. 5.2. I thought it was between the lookahead token and the
token before the dot, but perhaps Akim can clarify.
- bison info doc - precedence in recursive parsing, anand, 2019/02/03
- Re: bison info doc - precedence in recursive parsing, Anand Akhare, 2019/02/03
- Re: bison info doc - precedence in recursive parsing,
Hans Åberg <=
- Re: bison info doc - precedence in recursive parsing, Akim Demaille, 2019/02/04
- Re: bison info doc - precedence in recursive parsing, Hans Åberg, 2019/02/04
- Re: bison info doc - precedence in recursive parsing, Uxio Prego, 2019/02/04
- Re: bison info doc - precedence in recursive parsing, Hans Åberg, 2019/02/04
- Re: bison info doc - precedence in recursive parsing, Akim Demaille, 2019/02/05
- Re: bison info doc - precedence in recursive parsing, Hans Åberg, 2019/02/05
- Re: bison info doc - precedence in recursive parsing, Akim Demaille, 2019/02/05
- Re: bison info doc - precedence in recursive parsing, Hans Åberg, 2019/02/05
- Re: bison info doc - precedence in recursive parsing, Hans Åberg, 2019/02/10
- Re: bison info doc - precedence in recursive parsing, Akim Demaille, 2019/02/17