A couple of nits on the updated grammar:
*1*
Expression ::= Value
and, later,
Value:
...
| Expression action => eval
...
This alternative looks redundant.
*2*
UDFExpr ::= UDF OptionalExpressionSequence
ExpressionSequence ::= Expression OptionalExpressionSequence
OptionalExpressionSequence ::= ExpressionSequence
| Nothing
you probably know better, but why not just
UDFExpr ::= UDF Expression
just like FuncExpr?
Hope this helps,
rns
On Mon, Jul 21, 2014 at 12:26 AM, Paul Bennett <[email protected]>
wrote:
> >> In the paper's if X then Y else Z, X seems to be a (bound) variable (not
> >> sure if/how they convert it to boolean, perhaps by whether it has PDF or
> >> not), while it is a comparison in the grammar.
> >
> > The name "comparison" is just a notational thing for my convenience.
> > Oh, but yes. Yes, indeed. Variables are not allowed in the "X" slot in
> > my version. I'll have a think about that, and update the gist again
> > later.
>
> Okay. I've had more of a think, not just about the grammar but also
> about practical ways to implement the language. I may have strayed
> beyond the letter of the spec, but I suspect I've stayed within its
> spirit.
>
> URL as always is https://gist.github.com/PWBENNETT/8435996
>
>
> Thanks,
>
>
> --
> P/PW/PWBENNETT
>
> --
> You received this message because you are subscribed to the Google Groups
> "marpa parser" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
