Hello
this part of PostgreSQL grammar is hack and ambiguous. Output tree is
transformated in next step, so I needed only correct parsing.
I played with precedences and found solution (I can't to speak I
understand well, but it just works).
%left '[' ']'
%nonassoc ATTR_NAME
It's too big to make much sense of, but here's a couple of things you
can try:
I'd be surprised if it works. Have you tried column_method_name both
with and without brackets? The default is to ignore the brackets - what
happens then? How are the brackets interpreted?
without brackets it is re
On 23 Nov 2007, at 08:50, Pavel Stehule wrote:
I have gram file that works. But contains shift/reduce and I cannot to
correct it. What is worst, I don't see what is problem from bison log.
Look in the .output file that Bison generates for the state with the
conflicting rules, and apply token
On 23/11/2007, Evan Lavelle <[EMAIL PROTECTED]> wrote:
> If you want help with a grammar, you need to do one of two things:
>
> - post a grammar that fails. Put '%%' around it, make sure that there
> are no undefined rules, cut out all actions, and run Bison on it. Don't
> post everything: if 'expr
If you want help with a grammar, you need to do one of two things:
- post a grammar that fails. Put '%%' around it, make sure that there
are no undefined rules, cut out all actions, and run Bison on it. Don't
post everything: if 'expr' isn't relevant, add "expr : 'A' ;", for
example, or
- Sh
Hello
I have gram file that works. But contains shift/reduce and I cannot to
correct it. What is worst, I don't see what is problem from bison log.
columnref: relation_name
{
}
| relation_name indirecti
