Bruno Deferrari

> I'm continuing to question the need to have an executable form for each CL impl, i think it would be enough to have a `shen.lisp` library and a single...

> @tizoc My thinking (as seen in ShenScript and ShenSharp) is that a Shen implementation should be thought of as more of a library that gets imbedded in other applications...

@rkoeninger from my point of view, only SBCL binaries are required, 1) because it is the reference implementation, 2) I think it is the only one people use, 3) it...

For some reason the tests for the CLisp build fail on Linux, but I am not sure why.

So, the CLisp versions from Ubuntu Groovy, Ubuntu Bionic, and Ubuntu Xenial all behave differently, and the first two are broken. I will disable that for now because I don't...

Changelog here from what seems to have changed on CLisp by the Debian maintainers: https://metadata.ftp-master.debian.org/changelogs//main/c/clisp/clisp_2.49.20180218+really2.49.92-3_changelog

More here: https://sourceforge.net/p/clisp/clisp/ci/default/tree/src/NEWS

@rkoeninger same here, but turns out that newer versions of Ubuntu (and I guess Debian), use updated versions which don't behave the same as 2.49 (and they don't even seem...

I didn't think about this when making the change, but yes, the behaviour change comes with the modification. Not sure about what the "correct" behaviour should be, in Shen/Scheme it...

You have to declare everything that is not a sysfunc in the export list, otherwise it is going to be prefixed. For names internal to other packages you can just...