I admit that I am a passerby here but my impression is that things around
PicoLisp feel closed and this is not about the code itself.
In particular, there seems to be no public source code repository so source
history can only be inferred somehow from releases. I see that some people
already try to mirror it (see, e.g. https://github.com/taij33n/picolisp)
but since it is not "official" there's no development or associated
discussions. Since revision control is essential for any non-trivial
project, the lack of it is surprising.
Also there's no public bug tracker. Instead I have to subscribe to this
list so it is hard to track what happened to issues.
That said removing some friction for outsiders would help to keep things
2017-02-03 8:47 GMT+01:00 Alexander Burger <a...@software-lab.de>:
> Hi all,
> the future of PicoLisp is dark. I'm not sure if it can survive in packaged
> Ubuntu doesn't support it any more, probably due to the PIE (position
> independent executable) on x86-64.
> And at least on Android they seem to demand switching to Clang. The 32-bit
> versions of PicoLisp (pil32 and mini) which are written in C cannot be
> on Clang, because Clang doesn't support dynamically allocated arrays, which
> pil32 depends on. As far as I notices, pil64 also has trouble on
> :( Alex
> UNSUBSCRIBE: mailto:firstname.lastname@example.org?subject=Unsubscribe