Re: PicoLisp on windows

Sure. But tell me: What is faster? A tiny Picolisp interpreter binary, that entirely fits into 1st/2nd/3rd level cache, accesses memory without waitstaites - or a huge, multi gigabyte JIT engine, that, in itself, is a pure memory monster? My measurements show, that small, tiny interpreters -

Re: PicoLisp on windows

Gosh, no! On Wed, Mar 25, 2020 at 9:02 PM wrote: > Does anyone realize that there's an LLVM-based port of picolisp being > worked on by Alex? :) > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe > -- *Níl aon tinteán mar do thinteán féin. *[Irish Gaelic] (There is no

Re: PicoLisp on windows

Indeed Rick - it was listed in my original email as one of the options :) On Wed, Mar 25, 2020 at 6:02 PM wrote: > Does anyone realize that there's an LLVM-based port of picolisp being > worked on by Alex? :) > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >

Re: PicoLisp on windows

Does anyone realize that there's an LLVM-based port of picolisp being worked on by Alex? :) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: PicoLisp on windows

Hi to all! Before s.b. is reinventing wheels, like porting Picolisp onto .net, please consider Femtolisp, which is the base underlying Julia programming language JIT compiler. It's LLVM based and ultra fast, tiny and quite useful as PoC for implementing Picolisp on your own.

Re: PicoLisp on windows

Ah ok got it, thanks for the clarification. Hmm maybe you can also try the Emu of Pil64, its in C also. BR, Geo On Wed, Mar 25, 2020 at 2:23 PM C K Kashyap wrote: > By runtime I meant something beyond just the OS - in the case of .net , > you need the CLR (like the jvm in case of java). It's

Re: PicoLisp on windows

By runtime I meant something beyond just the OS - in the case of .net , you need the CLR (like the jvm in case of java). It's just that windows machines come with CLR so it is not apparent. Regards, Kashyap On Tue, Mar 24, 2020 at 10:08 PM George-Phillip Orais < orais.georgephil...@gmail.com>

Re: PicoLisp on windows

Hi Kashyap, That's also one of my plan so it will work on Linux and Mac, but will see coz it will be redundant especially for Linux. miniPicoLisp is indeed pure PicoLisp and ideally for embedded systems, but I'm not sure what you mean "not needing any runtime". BR, Geo On Wed, Mar 25, 2020 at

Re: PicoLisp on windows

It will be great if I could have a starting point to extend miniPicoLisp - hasn't anyone tried to add networking to miniPicoLisp :) Regards, Kashyap On Tue, Mar 24, 2020 at 9:36 PM C K Kashyap wrote: > Thanks all, > > Hey Geo - perhaps you should use .Net core :) - I look forward to your >

Re: PicoLisp on windows

Thanks all, Hey Geo - perhaps you should use .Net core :) - I look forward to your implementation. I'd still like to figure the possibility of adding to miniPicoLisp - I like the idea not needing any runtime :) Regards, Kashyap On Tue, Mar 24, 2020 at 8:43 PM r cs wrote: > Ersatz is much

Re: PicoLisp on windows

Ersatz is much more functional than minipicolisp and includes basic TCP networking. Regards, rcs On Tue, Mar 24, 2020 at 10:51 PM C K Kashyap wrote: > Thanks rcs, > I just checked - at the very least Ersataz has "call" implemented!!! > ...makes it more useful that miniPicoLIsp. > Regards, >

Re: PicoLisp on windows

Hi Kahsyap et al, First of all, I hope everyone here and everyone's family are doing well, safe and far from the COVID19 danger. Today I started to work from home because yesterday the report came that one worker from different company but in the same building of our office is COVID19 positive,

Re: PicoLisp on windows

Thanks rcs, I just checked - at the very least Ersataz has "call" implemented!!! ..makes it more useful that miniPicoLIsp. Regards, Kashyap On Tue, Mar 24, 2020 at 7:27 PM C K Kashyap wrote: > Hi rcs, > I had not considered Erstaz since I assumed that it is equivalent in > capability to

Re: PicoLisp on windows

Hi rcs, I had not considered Erstaz since I assumed that it is equivalent in capability to miniPicoLisp and has the added requirement of JVM. While I am sure about the JVM part, I am not so sure about the capabilityis that not so? Regards, Kashyap On Tue, Mar 24, 2020 at 7:03 PM r cs wrote:

Re: PicoLisp on windows

Kashyap: Have you considered Ersatz on Windows? Regards, rcs On Tue, Mar 24, 2020 at 6:55 PM C K Kashyap wrote: > Hi All, > I've been using PicoLisp under docker on my windows machine but a > challenge that I face is in my ability to share the scripts with my > colleagues. It would be awesome

Re: picolisp on windows

Oops, I should have looked more closely. I do see the .src files :) Thanks! On Tue, Feb 5, 2019 at 6:07 AM Alexander Burger wrote: > Hi Kashyap, > > > Anyway, I could not find the java sources - I could only find the > compiled > > jar file. Are the java sources available? > > They are in fact

Re: picolisp on windows

Hi Kashyap, > Anyway, I could not find the java sources - I could only find the compiled > jar file. Are the java sources available? They are in fact included in the PicoLisp distro, however not as *.java files, but as ersatz/sys.src ersatz/fun.src The script mkJar takes them, builds a

Re: picolisp on windows

Thanks for the tips rcs, Yes indeed I was able to build minipicolisp on windows using mingw32. The best part is that I could take the generated exe and run it on another machine :) My goal is to understand picolisp implementation and perhaps switch to it as my programming environment. I cant wait

Re: picolisp on windows

Kashyap: Under MinGW32 miniPicoLisp fails to build without two tweaks to the Makefile: 1. Remove the -lc switch in this line: *$(CC) -o $(bin)/picolisp $(picoFiles:.c=.o) -lc -lm* 2. After doing the above an executable will be produced, but the *strip* command in the line after that will also

Re: picolisp on windows

Yes -- good catch Alex, thanks. On Mon, Feb 4, 2019 at 2:47 AM Alexander Burger wrote: > On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote: > > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the > EXE > > from where I built it in msys under >

Re: picolisp on windows

Hi Alex, I wonder if libuv can substitute for POSIX? Has there been any work in that direction? Regards, Kashyap On Sun, Feb 3, 2019 at 11:47 PM Alexander Burger wrote: > On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote: > > I've personally built PicoLisp under MinGW-32 on Windows 7, copied

Re: picolisp on windows

On Sun, Feb 03, 2019 at 10:25:13PM -0500, r cs wrote: > I've personally built PicoLisp under MinGW-32 on Windows 7, copied the EXE > from where I built it in msys under /MinGW/msys/1.0/home/myUser/picoLisp/src > to some place else on the system, and then just run it from a command > prompt. Using

Re: picolisp on windows

Thanks rcs, I'll go ahead and start using picolisp built with mingw-32 for now and familiarize myself with it. Thanks for the confirmation - it's good to know that it works :) Regards, Kashyap On Sun, Feb 3, 2019 at 7:31 PM r cs wrote: > Kashyap: > > In case you didn't know this, MinGW produces

Re: picolisp on windows

Kashyap: In case you didn't know this, MinGW produces MSVC executables compatible with normal Windows, so you just can grab the EXE out of the msys environment and run it on any computer where the MSVC redistributable from Microsoft has already been installed. I've personally built PicoLisp

Re: PicoLisp on Windows WSL first tryout fails ...

Joe Bogner writes: Hey Joe, > > For WSL, you need to build picoLisp on a linux machine and then transfer > it down. You can follow the download/install instructions, but here is > generally what I did maybe I don't really understand what you mean by transfer down, but in my

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Arie, > After that picolisp installed just fine. So far, so good! > > I notice that the package name is picolisp17.12+20180218-1, which seems to > be version 17.12 (looking at that name), > but "pil -version" says 18.2.17. How about that? That's OK, an intermediate version release :) ♪♫

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Alexander, just posted my success story :-) I just downloaded the latest PicoLisp deb package and tried to install with dpkg. It failed, because it missed libssl1.1. After quite a bit of searching I thought I had to upgrade Linux (apt-get upgrade). So, I did that, because it wouldn't hurt

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Arie, > So, I tried it another way by just installing the Debian package PicoLisp: >sudo apt-get install picolisp > and indeed, now starting pil just works. However, it is an older version ( > *15.11.0*). Yes, it is Debian "stable". > On this page: >

Re: PicoLisp on Windows WSL first tryout fails ...

​Hi Joe, going the Vagrant way will be difficult. On this (older HP) PC I've tried many times to get Linux to run in e.g. VirtualBox and also VMWare. To date I can't get it to work. In the past I ran Linux quite a few times under VirtualBox and VMWare on other computers. Maybe it has to do with

Re: PicoLisp on Windows WSL first tryout fails ...

Arie, For WSL, you need to build picoLisp on a linux machine and then transfer it down. You can follow the download/install instructions, but here is generally what I did ON LINUX 1. wget https://software-lab.de/picoLisp.tgz 2. tar -zxvf picoLisp.tgz 3. cd picoLisp/src 4. make 5 cd ../src64 6.

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Philipp, Arie, > pil is just a wrapper around picolisp, it loads a few libraries etc as Yes, but > standard, but it relies on the intepreter being at /usr/bin/picolisp, This is not completely correct. Note that there are two 'pil's in the distribution: One in bin/ #!/usr/bin/picolisp

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Philip, just copied all stuff from bin to /usr/bin/picolisp and then tried to run pil. But same error shows up. So I guess I'll have to wait a bit for the PicoLisp guru's ;-) Thx anyway. Apperciate it! /Arie 2018-04-17 13:01 GMT+02:00 Philipp Geyer : > Hi Arie, > > pil

Re: PicoLisp on Windows WSL first tryout fails ...

Hi Arie, pil is just a wrapper around picolisp, it loads a few libraries etc as standard, but it relies on the intepreter being at /usr/bin/picolisp, which it is not in your case. You can either try changing the shebang at the top of pil from #!/usr/bin/picolisp /usr/lib/picolisp/lib.l to

Re: PicoLisp on Windows

After installing WSL I'm going to install/make PicoLisp. I guess I now should use the default installation steps here: https://picolisp.com/wiki/?home > ​Otherwise, grab the latest version - [picoLisp.tgz] - unpack it, > follow the instructions from the INSTALL file, and then check out the >

Re: PicoLisp on Windows

Hi Joe, ok. I'll try WSL then. Will let know about my findings. Maybe others can profit as well (Philip?) Thx /Arie Op ma 16 apr. 2018 18:10 schreef Joe Bogner : > Hi Arie, > > I would like to send a more detailed reply later. I'm the author of the > flinux writeup. It's

Re: PicoLisp on Windows

Hi Arie, I would like to send a more detailed reply later. I'm the author of the flinux writeup. It's been a few years and things don't work as nicely as they did back then. I retested some the writeup today. I was unable to get the flinux static option working. I was able to get flinux dynamic

Re: PicoLisp on Windows

Based on the instructions on the site, it looks like the next steps are to build pil on Linux, and then run the linux binary on Windows through flinux. I have not tried pil in WSL yet (my only Windows text machine is Win7), and I don't think that's a solution for my specific problem (to have a