Most changes are variable renamings because elm does not allow masking
a visible name anymore.
Deal with changes in the standard library, especially in the Parser
interface.
Source files must now start with a capital letter.
Dockerfile: remove unneeded dependencies, install nodejs from debs.
Remove the redundant Maybe from the return value of readstring.
Stop embedding the colon in keyword represenation.
Some implementations send non-UTF-8 codes (i.e. es6 when showing
function representations). So use latin1 which is probably closer to
what most things are outputting to the terminal.
Explictly select python 3. The `python2` and `python` packages will
be removed from Ubuntu. Until each call site is fixed, install a
/usr/local/bin/python symbolic link as a non-intrusive work-around
(.deb packages do not interfer with /usr/local).
Add an explicit maintainer for bbc-basic.
Undo some cosmetic changes in order to reduce the global diff, this
merge request will probably be sqashed before acceptance.
Move lib{readline,edit}-dev out of the generic part.
Use existing .deb packages for GHDL and vim.
The modified implementations have been tested on Debian bullseye.
* prefer later Ubuntu image, hopefully reducing the image count
* for Ubuntu versions, prefer numerical versions to unsorted codenames
* prefer packaged build systems to local rebuilds
* prefer the current default version of each build system
* delegate resolution of indirect dependencies to apt
* xslt: remove intermediate run script. The initial motivation is to
provide an explicit path to the python3 interpreter, as the
versioned executable is not always in PATH.
* Add DEBIAN_FRONTEND=noninteractive to some Dockerfiles. This is to
workaround tzdata which prompts interactively by default.
* Debian/Ubuntu do not ship a python->python2 link by default.
* With the improved logo implementation in another branch, there is no
need anymore to tweat the garbage collector settings.
* logo: use upstream brandy compiler (instead of building).
* guile: adjust deb-src mechanism to build ucblogo and workaround doc
build bug.
c.2:
By updating to 24.04 we get around an error with declarations after
labels which is allowed in more recent compiler versions.
make:
With older make, the newer make code results in this error:
../make/readline.mk:13: *** unterminated call to function 'eval': missing ')'. Stop.
Newer versions of make work fine.
perl6:
With older rakudo, this error occurs:
user> (let* (DEBUG-EVAL false) (- 3 1))
Cannot resolve caller Numeric(types::MalFalse: ); none of these signatures match:
ocaml:
Fixes build error that happens with older versions of ocaml:
ocamlopt -a types.ml reader.ml printer.ml env.ml core.ml -o mal_lib.cmxa
File "env.ml", line 15, characters 8-21:
Error: Unbound value Data.find_opt
objpascal:
With older compiler, the following error occurs:
user> (apply str (seq "this is a test"))
*** Error in `../objpascal/stepA_mal': corrupted size vs. prev_size: 0x000000000246c360 ***
See issue #587.
* Merge eval-ast and eval into a single conditional.
* Expand macros during the apply phase, removing lots of duplicate
tests, and increasing the overall consistency by allowing the macro
to be computed instead of referenced by name (`((defmacro! cond
(...)))` is currently illegal for example).
* Print "EVAL: $ast" at the top of EVAL if DEBUG-EVAL exists in the
MAL environment.
* Remove macroexpand and quasiquoteexpand special forms.
* Use pattern-matching style in process/step*.txt.
Unresolved issues:
c.2: unable to reproduce with gcc 11.12.0.
elm: the directory is unchanged.
groovy: sometimes fail, but not on each rebuild.
nasm: fails some new soft tests, but the issue is unreproducible when
running the interpreter manually.
objpascal: unreproducible with fpc 3.2.2.
ocaml: unreproducible with 4.11.1.
perl6: unreproducible with rakudo 2021.09.
Unrelated changes:
Reduce diff betweens steps.
Prevent defmacro! from mutating functions: c forth logo miniMAL vb.
dart: fix recent errors and warnings
ocaml: remove metadata from symbols.
Improve the logo implementation.
Encapsulate all representation in types.lg and env.lg, unwrap numbers.
Replace some manual iterations with logo control structures.
Reduce the diff between steps.
Use native iteration in env_get and env_map
Rewrite the reader with less temporary strings.
Reduce the number of temporary lists (for example, reverse iteration
with butlast requires O(n^2) allocations).
It seems possible to remove a few exceptions: GC settings
(Dockerfile), NO_SELF_HOSTING (IMPLS.yml) and step5_EXCLUDES
(Makefile.impls) .
This should be the default if things are working correctly so logging
this now is just noise that causes the summaries that are relevant to
get folded in the UI.
- Update to ubuntu 24.04 Dockerfile and add labels.
- update to working version of ffi-napi
- Remove from miniMAL-core.json the things that overlap with the builtin
core functionality that miniMAL now provides in 1.2.2.
- Update ARGS variable to argv to align with how 1.2.2 now does command
line parameters.
The set-output mechanism is deprecated for security reasons so set
environment variable outputs in GITHUB_OUTPUT instead. Change
get-ci-matrix.py to output the env file settings to stdout and move all
debug output to stderr.
vivid packages are no longer available.
There are still implementations that use vivid because updating to
xenial was not sufficient to get them working again.
A major maintainability issue for years has been that the CI assumes
that a docker image for the implementation exists in Docker's registry
(named kanaka/mal-test-IMPL). This means the upstream maintainers have
to be involved in the PR loop to build the implementation Dockerfile,
push to the docker registry and then have the PR submitter re-run CI.
To address this, in ci.sh, the docker-build-push action will try to pull
the image and then continue as normal. If the pull fails then it will
build the image and push it (if the build is running in the context of
the upstream repo's main branch) and then continue.
Also, this switches to using ghcr.io as the default repo for images
which will make image transfer more local (during CI) and hopefully
a fair bit faster (and avoid potential docker pull limits).
Add a steps to the GHA main workflow that do a docker login to ghcr.io
and then call `ci.sh docker-build-push ${IMPL}`.
Most of the time, the WASI fd_read call returns the whole line including
the newline. Other times, it returns everything except the newline. So
before stompiing the newline, check for that condition. This fixes the
WASI based wasm implementations (wasmtime, wasmer, lucet).
