[sqlite] How this /*A-overwrites-S*/ should work ?

Thanks for the answer ! > Wed Feb 24 2016 6:38:46 pm CET CET from "Richard Hipp" > > > The /*A-overwrites-S*/ comment is processed by Lemon, and Lemon has no > knowledge of #ifdefs. > > > I can understand that but it will confuse other people like it did to me ! Cheers !

[sqlite] How this /*A-overwrites-S*/ should work ?

I solved it setting a variable before " /*A-overwrites-S*/", but I's still confusing it's usage inside a wrapped "#ifdef" that supposed only will be executed conditionally. Cheers ! oneselect(A) ::= SELECT|XSELECT(S) distinct(D) selcollist(W) from(X) where_opt(Y)

[sqlite] How this /*A-overwrites-S*/ should work ?

Here is the full changes I did in parser.y: ? %endif SQLITE_OMIT_COMPOUND_SELECT oneselect(A) ::= SELECT|XSELECT(S) distinct(D) selcollist(W) from(X) where_opt(Y) groupby_opt(P) having_opt(Q) orderby_opt(Z) limit_opt(L). { #if SELECTTRACE_ENABLED ? Token s = S;

[sqlite] How this /*A-overwrites-S*/ should work ?

Hello ! I have a modification on the parser.y for my own purposes and it was been parsed till the introduction of " /*A-overwrites-S*/" and it seems that something is wrong on parser.y see bellow, after the SELECT specification the " /*A-overwrites-S*/" is wrapped by "#if SELECTTRACE_ENABLED"

[sqlite] How this /*A-overwrites-S*/ should work ?

On 2/24/16, Domingo Alvarez Duarte wrote: > I solved it setting a variable before " /*A-overwrites-S*/", but I's still > confusing it's usage inside a wrapped "#ifdef" that supposed only will be > executed conditionally. The /*A-overwrites-S*/ comment is processed by Lemon, and Lemon has no

[sqlite] How this /*A-overwrites-S*/ should work ?

On 2/24/16, Domingo Alvarez Duarte wrote: > Hello ! > > I have a modification on the parser.y for my own purposes and it was been > parsed till the introduction of " /*A-overwrites-S*/" and it seems that > something is wrong on parser.y see bellow,\ The /*A-overwrites-S*/ comment is a hint to