nqp VS json

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.

An example is the 40 line JSON::Tiny::Grammar of the Raku module JSON::Tiny. Raku grammars are analytical grammars. This one corresponds to the grammar of JSON defined by "RFC7159, which is a superset of ECMA-404, in that it permits any value as a top-level JSON string, not just arrays and objects".

For example, the JSON::Tiny grammar uses no backtracking, has almost entirely declarative rules, but leans on the default Turing complete powered top down recursive descent invocation of those rules to drive its predictive parsing.

A `rule` is a `token` with `:sigspace` also enabled (whitespace becomes the same as a call to `<.ws>`).

The only one of those that really looks anything like traditional regexes is the `value:sym` token. (Raku replaced non capturing grouping `(?:…)` with `[…]`, and character classes `[eE]` with `<[eE]>`)

This code was copied from https://github.com/moritz/json/blob/master/lib/JSON/Tiny/Gra... but some parts were simplified to be slightly easier to understand. Mainly I removed the Unicode handling capabilities.

It will generate a tree based structure when you use it.

    my $json = Q:to/END/;

For JSON specifically, here's a simple serializer/deserializer (Grammar, Actions).