NQP - Not Quite Perl
NQP is Copyright (C) 2009-2019 by The Perl Foundation. See LICENSE for licensing details.
This is "Not Quite Perl" -- a lightweight Raku-like environment for virtual machines. The key feature of NQP is that it's designed to be a very small environment (as compared with, say, raku or Rakudo) and is focused on being a high-level way to create compilers and libraries for virtual machines like MoarVM , the JVM, and others.
Unlike a full-fledged implementation of Raku, NQP strives to have as small a runtime footprint as it can, while still providing a Raku object model and regular expression engine for the virtual machine.
Building from source
To build NQP from source, you'll just need a
make utility and
Perl 5.8 or newer. To automatically obtain and build MoarVM you may also need a
NQP directly from its repository:
$ git clone git://github.com/Raku/nqp.git
If you don't have git installed, you can get a tarball or zip of NQP from github by visiting http://github.com/Raku/nqp/tree/master and clicking "Download". Then unpack the tarball or zip.
NQP can run on three different backends:
JDK 1.9 (also known as
JDK 9) or higher.
Decide on which backends you want it to run, and configure and build it as follows:
Once you have a copy of NQP, build it as follows:
$ cd nqp $ perl Configure.pl --backends=moar,jvm $ make
If you don't have an installed MoarVM, you can have
Configure.pl build one for you by passing the
--gen-moar option to it as well.
make step will create a
nqp.exe executable in the current directory. Programs can then be run from the build directory using a command like:
$ ./nqp hello.nqp
By default, NQP searches for the MoarVM executable and installs to the directory
./install. You can change that with the
--prefix option to Configure.pl.
Once built, NQP's
make install target will install NQP and its libraries into the same location as the MoarVM installation that was used to create it. Until this step is performed, the
nqp executable created by
make above can only be reliably run from the root of NQP's build directory. After
make install is performed the executable can be run from any directory.
NQP compiler is invoked without an explicit script to run, it enters a small interactive mode that allows statements to be executed from the command line. Each line entered is treated as a separate compilation unit, however (which means that subroutines are preserved after they are defined, but variables are not).
On OS X, it appears that configuration fails in some configurations:
3rdparty/libuv/include/uv-darwin.h:26:11: fatal error: 'mach/mach.h' file not found
Should this happen to you, then a solution might be the following:
$ cd MoarVM/3rdparty/libuv/include $ ln -s /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/mach $ cd ../../../.. $ # run the Configure again
Note that the 10.9 in the above, represents the major version of OS X being used. On Mavericks use 10.9 (like above), on Yosemite use 10.10.
NOTE: there's no end-user support for NQP and the behaviour can change without notice. It's a tool for writing Raku compilers, not a low-level module for Raku programmers.
The examples directory is a good place to start, with the loops and other files. Opcodes are listed in the docs directory. NQP also has built-in routines listed in the docs directory. You can use NQP from this release, it will be already installed if you have built Raku from scratch.
The best thing before playing with it/hacking on it is to contact pmurias via IRC at
#raku on irc.freenode.org. We depend on
node.js at least 10.10.0
$ perl Configure.pl --backends=moar,js $ make
Currently it needs to be run like:
$ ./nqp-js file.nqp
If you are developing
nqp-js, you may want to pass the
--link option to configure to have the
nqp-runtime linked instead of installed
$ cd src/vm/js/nqp-runtime; npm link . $ perl Configure --backends=moar,js