@Jean-Damien: I am glad you brought this up. Marpa::R2 is not totally
frozen with respect to new features, but it *is* in a deep, deep chill.
It is not sufficient for a new feature to be possible and desirable --
the new feature also has to be of low risk to the present application
base and to make sense in terms of Marpa's overall roadmap, including
R3. (Marpa::R2 bugs, of course, continue to get top priority.)
In this case, the doit() method is very low risk (a wrapper around
present functionality), and it's seems like a good way to try out some
new ideas. So that's why I am not treating it as subject to the "chill"
on new Marpa::R2 features.
But it's worth pointing out that, when it comes to new features, the
answer will usually be "No, wait for R3".
-- jeffrey
On 08/15/2014 01:49 PM, Durand Jean-Damien wrote:
Ok, point taken.
Marpa::R2 has now only a bug-fix only roadmap isn't it Jeffrey ? This
sounds like a feature request.
About the name , hmmm eval() ?
Le vendredi 15 août 2014 22:37:29 UTC+2, Christopher Layne a écrit :
Yes but value returns a ref to a ref so the user can still do that
already.
--
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]
<mailto:[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.
