On Mon, 26 Sep 2005, Derek M Jones wrote:
My point here is that the current functionality seems natural and necessary
for all GLR parsers. Do you disagree?
Either before or after is necessary. Both would be helpful.
I'm not sure the term 'natural' can be applied to a human
invention.
I see
On 23 Sep 2005, at 03:33, Derek M Jones wrote:
If I knew in advance (that is, before the action associated
with a rule was executed) I could set some variable that
could be tested in the action to decide whether to handle
the common case or whether some kind of semantic ambiguity
resolution was
On Friday 16 September 2005 20:28, Evan Lavelle wrote:
> struct yystype {
> ...
> antlr::RefToken tok;
> antlr::RefASTast;
> };
>
> #define YYSTYPE yystype
Yupp, that is an attractive solution from a memory management perspective.
However, I have trouble with connecting flex to t
On Mon, 26 Sep 2005, Derek M Jones wrote:
This pre-merge user function would be an extra feature. I don't foresee
myself using it, so I really can't justify spending my own time
implementing it and arguing for its acceptance.
Thanks for considering it. The implementation is trivial and
I hop
Joel,
My point here is that the current functionality seems natural and
necessary for all GLR parsers. Do you disagree?
Either before or after is necessary. Both would be helpful.
I'm not sure the term 'natural' can be applied to a human
invention.
Ok, so let's change its name.
%premerge
On Mon, 26 Sep 2005, Derek M Jones wrote:
Does anybody know why the decision was made to have the %merge
function called last? This choice seems to be very suboptimal.
The merge function's job is to merge the semantic values constructed by the
two actions. If it were called before the acti
On Fri, 23 Sep 2005, Derek M Jones wrote:
Unfortunately the function associated with %merge is called
AFTER the actions are executed.
Does anybody know why the decision was made to have the %merge
function called last? This choice seems to be very suboptimal.
The merge function's job is
Joel,
Does anybody know why the decision was made to have the %merge
function called last? This choice seems to be very suboptimal.
The merge function's job is to merge the semantic values constructed by
the two actions. If it were called before the actions, what would it
merge?
Ok, so