Subject Re: [Firebird-Architect] Named arguments for SP
Author Nando Dessena

A> The ambiguity I told already exist with UPDATE for example, and you can
A> resolve it with :variable.

UPDATE has a SET clause; I can't see the ambiguity.

A> But also I think Dmitry's syntax break the parser, it's not LALR(1) when
A> "x = 1" is a valid expression.

Would that (not being 100% LARL(1) - assuming the current grammar is)
be such a huge problem?

Nando Dessena