>the future of PicoLisp is dark.
That sounds about right...I run openbsd and they've just made v6.0
Linux- incompatible because they don't like the way it's going.
Pil64 compiles fine on the latest openbsd BTW.
Assuming that Wine packages are more numerous than Picolisps...you could do
a native Windows version in Powerbasic for Wine. Not only would this up
your linux exposure but Linux is only 2% of the desktop market whilst
Windows has about 80%,
I smiled when I saw your reasons for moving from C to asm because
Powerbasic does ALIGN etc in it's stride without needing to drop down to
it's industrial strength built in assembler. It also runs on win95 to 10
and produces exes for the same, both without any dependencies. How about
that for stable. It also has very fast dynamic arrays.
I'd prefer to work in 64 bit asm but would be very happy to assist you in
any way I can to see Picolisp do well as I'm sure others would be. Whatever
you decide just let us know how we can help. I'm very new to Picolisp but
can already see that it's much too good not to do well.
On 3 February 2017 at 08:41, Lindsay John Lawrence <
> I hope it is not dark.
> I am just starting on my adventure using PicoLisp and having a wonderful
> time of it.
> Having said that, I have never used any of the distribution packages.
> Picolisp is simple to compile with minimal dependencies. Thank you for
> that as well Alex.
> On my laptop machine I have just been compiling the latest download
> whenever it is available.
> It also runs extremely well in a minimal TinyCore Linux image.
> Tinycore+Picolisp+core system utils makes for a great sandbox in a few
> tens of megabytes as either a virtualbox or as a bootable stick
> I think I also compiled it on Android a few months ago (in Termux) without
> issue. I'll have to try it again there.
> Keep the light on :)
> On Thu, Feb 2, 2017 at 11:47 PM, 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,
>> pil32 depends on. As far as I notices, pil64 also has trouble on
>> :( Alex
>> UNSUBSCRIBE: mailto:firstname.lastname@example.org?subject=Unsubscribe