EventExpressionLanguage VS nqp

I’ve also been playing with a new type of grammar idea, grammar for events, I’m also waiting for rakuAST for making it a slang. Here are my first tests: https://github.com/FCO/EventExpressionLanguage

hi! I was looking at REPL-like evaluation of code from here and here, and tried to make a very small version for it, yet it fails:

Second, any "inheritance" is optional. Quoting nqp's 6model overview with my added emphasis:

Considering it has a compiler (which generates an NFA), I do not think it is fair to call it an interpreter.

When I mention the Actor model, I specifically mean the Actor model, not "an actor model". That is to say, a mathematical theory, not an implementation. In contrast, ponder what you mean by "an object model". When I mention the "metamodel", I specifically mean "a framework [that] does not contain an implementation of classes, interfaces, roles, prototype objects and so forth".

NQP is a compiler like MiniPerl for Perl 5. It is a bootstrapping tool which helps to compile the Raku parts of Rakudo and compile the libraries before running have compiled the libraries. Unlike MiniPerl for Perl 5 (which is an interpreter that can interpret all Perl syntax but miss some batteries: means without modules mixing Perl code and native code), NQP can only compile a "simplified Raku". NQP refers to both the compiler and the source code contained in files with the ".nqp" extension.

I focus on the Raku stack: the compiler Rakudo which targets the compiler compiler NQP which targets multiple backends including MoarVM. (Which

NQP is a compiler compiler toolkit that targets multiple backends: JVM, JS, and MoarVM.