In one sense, Marpa is very much embedded in Perl 5 -- it's core is in C
and it is accessed via an XS module.
On the other hand, you could not really "embed" Marpa into Perl 5's own
*parsing*, and I think that's what we're talking about. We speak of
parse "engines" and the metaphor is powerful -- replacing a parse engine
in a language is like a car model siwtching to a different model of
engine. An automotive engineer has no real middle ground available --
he is forced to decide to go one way or the other.
This, by the way, makes GCC's decision to throw out yacc and LALR
parsing, in favor of recursive descent, a major event in the history of
computer parsing. They had to have been very unhappy with
LALR/yacc/bison to do that.
-- jeffrey
On 03/11/2014 02:35 PM, Ross Attrill wrote:
Interesting reading. You say that it would be impossible to embed
Marpa into Perl 5. However, I wonder if it could not be used in one
of the implementations of Perl 6, Perl 11 http://perl11.org/ or Moe
projects. Something to watch for I guess.
On Wednesday, 12 March 2014 05:09:46 UTC+11, Jeffrey Kegler wrote:
I have a new blog post
<http://jeffreykegler.github.io/Ocean-of-Awareness-blog/individual/2014/03/kv.html>
up: "Language design has been like shooting crap in a casino that
sets you up to win a lot of the first rolls before the laws of
probability grind you down."
--
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.
