This is a pure python implementation of the MUV 2.0 compiler. It takes C-like MUV language source code, and compiles it to the more inscrutable forth-based MUF language, suitable for uploading to an fb6 (or later) Fuzzball MUCK chat server.
Creating MUF programs is an ugly, painful, nearly write-only experience, and that's coming from the coder who designed most of the language. Why spend massive amounts of time debugging and keeping track of stack items, when you can write code in a more modern, readable language?
Instead of writing cryptic code like:
: showspecies[ -- ret ] var obj loc @ contents_array foreach obj ! pop obj @ player? if obj @ "species" getpropstr dup not if pop "Unknown" then obj @ "sex" getpropstr dup not if pop "Unknown" then obj @ "%-30D %-10s %-30s" fmtstring me @ swap notify then repeat ;
You can write:
func showspecies() { for (var obj in contents_array(loc)) { if (player?(obj)) { ftell( "%-30D %-10s %-30s", obj, getpropstr(obj, "sex") || "Unknown", getpropstr(obj, "species") || "Unknown" ); } } }
Install using PyPi:
pip install pymuv
Installing from sources:
python3 setup.py build install
The muv
program expects the input MUV source file to be given on the
command-line. The MUF output will, by default, be written to STDOUT
.
Error messages will be printed to STDERR
, and the return code will be
non-zero if errors were found:
muv sourcefile.muv >outfile.muf
You can use -w PROGNAME
to wrap the output in MUF editor commands:
muv -w cmd-whospecies whospecies.muv >whospecies.muf
Using -o OUTFILE
will write the output MUF code to OUTFILE instead
of STDOUT:
muv -o whospecies.muf whospecies.muv
Adding a -d
to the command-line will add debugging code to the MUF output.
Each line of MUV will add code like: "foo.muv:23" pop
to the MUF output:
muv -d -o whospecies.muf whospecies.muv
- Language reference: <https://github.com/revarbat/pymuv/blob/master/MUVREF.rst>