nqp VS MoarVM

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.

Implement return prioritization #1786: superseeded

Now, as to how that's done at the low level, and whether the way it's done is a good way to do it, well, I can't help. Suffice to say, the main place to look for how this is handled at the low-level is MoarVM. I dug around for a couple minutes and have a link to a commit from nearly a decade ago. Does that help?

For a class the default representation is P6Opaque. This is one of a few dozen stock representations that Raku requires compiler backends implement as standard. See, for example, the 46 .c/.h pairs of C89 source files in the relevant MoarVM directory. A quick glance at the names of the source code files should paint a broad picture. A look at their code will fill in some details.

I'm hoping someone who knows C89 can take a quick gander at the C89 code implementing 47 representations in here and comment on it.

This is (yet another) very un(der)documented Raku feature (over a decade after it was introduced!), but one can browse what looks to me like reasonably clean and commented C89 code implementing 47 representations in the relevant MoarVM directory.

FROM alpine:latest as base ARG RAKU_RELEASE=2021.12 ENV PKGS="git make gcc musl-dev perl linux-headers bash" RUN apk update && apk upgrade \ && apk add --no-cache $PKGS \ && git clone --depth 1 --branch ${RAKU_RELEASE} https://github.com/MoarVM/MoarVM.git \ && cd MoarVM \ && perl Configure.pl --prefix /usr \ && make --print-data-base \ && make install\ && cd .. \ && git clone --depth 1 --branch ${RAKU_RELEASE} git://github.com/Raku/nqp.git \ && cd nqp \ && perl Configure.pl --backends=moar --prefix /usr \ && make install \ && cd .. \ && git clone --depth 1 --branch ${RAKU_RELEASE} https://github.com/rakudo/rakudo.git \ && cd rakudo \ && perl Configure.pl --backends=moar --prefix /usr \ && make install \ && ls /usr/share/nqp/ FROM alpine:latest ARG UID=1000 LABEL version="0.5.0" maintainer="[email protected]" raku_release=${RAKU_RELEASE} raku_user_uid=${UID} COPY --from=base /usr/lib/libmoar.so /usr/lib COPY --from=base /usr/share/nqp/ /usr/share/nqp COPY --from=base /usr/share/perl6/ /usr/share/perl6 COPY --from=base /usr/bin/moar /usr/bin/nqp /usr/bin/raku /usr/bin/perl6 /usr/bin/rakudo /usr/bin/ RUN mkdir /github \ && addgroup -S raku && adduser -S raku -G raku --uid ${UID} USER raku WORKDIR /home/raku ENTRYPOINT ["raku"]

Visit the MoarVM project's home page and/or its github repo.

MoarVM's representation is very cool https://github.com/MoarVM/MoarVM/blob/master/docs/strings.asciidoc