Picolisp has a release archive readily downloadable here... http://software-lab.de/down.html. In my limited experience with picolisp, it actually reminds me of sqlite ( http://sqlite.org) in its approach...
"Small, Fast, Reliable. Chose any three" Sqlite seems to have a particularly effective source management model and an astonishingly active mailing list. The only way to get the latest (or even moderately recent) version of sqlite is to download a pre-compiled snapshot from the website or build it yourself. Both very trivial tasks for the motivated. The source repo for sqlite is Fossil ( http://www.fossil-scm.org/index.html/doc/trunk/www/index.wiki). Fossil, written for sqlite, holds all the code, history and docs in a sqlite database. How 'lisp' is that? ;) Alex, Picolisp has the wiki, vip, built in database all written in picolisp... is an scm such a big leap? Just a thought :) /Lindsay On Mon, Feb 20, 2017 at 10:19 AM, Jakob Eriksson <[email protected]> wrote: > > > I would love for the public repo to be on github! > > I think for many, an open source project does not really exist, > unless it is on Github. We should also try to resurrect somehow, > the [picolisp] tag on Stack Overflow. > > Given that it is encouraged to put in official documentation in the > form of Q/A on Stack Overflow, I think we could have a coordinated > effort from here to do it. > > > > > On 2017-02-20 18:15, Petr Gladkikh wrote: > > 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 > > <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 > > running. > > > > > > 2017-02-03 8:47 GMT+01:00 Alexander Burger <[email protected] > > <mailto:[email protected]>>: > > > > Hi all, > > > > the future of PicoLisp is dark. I'm not sure if it can survive in > > packaged > > distribution. > > > > 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 compiled > > on Clang, because Clang doesn't support dynamically allocated > > arrays, which > > pil32 depends on. As far as I notices, pil64 also has trouble on > > Clang/Android. > > > > :( Alex > > -- > > UNSUBSCRIBE: mailto:[email protected] > > <mailto:[email protected]>?subject=Unsubscribe > > > > > > > > > > -- > > Petr Gladkikh > -- > UNSUBSCRIBE: mailto:[email protected]?subject=Unsubscribe >
