<taleon>
I discovered PicoLisp by chance yesterday and so far I'm pretty enthusiastic about it. I've tried 100 times to familiarize myself with Common Lisp and have always failed due to the complexity of the commands. I wish you all a happy new year.
<abu[7]>
Thanks! To you too a happy new year :)
<anddam>
taleon: new to lisps altogheter?
<anddam>
taleon: I was as well and I have been suggested not to approach plisp for that, as nice, tiny and well-documented as it is it's not for beginners
<taleon>
I have a little beginner experience with CL and Scheme. Personally I am more a fan of assembler than C and professionally I am a technician and administrator and have been programming on the C64 since my childhood. That's why PicoLisp appeals to me.
<taleon>
I like simple things. :-)
<taleon>
However. I'll just have a look at PL and play with it a bit.
<abu[7]>
"assembler" and "simple" is well in the spirit of PicoLisp
<abu[7]>
Though with Pil21 it moved from Asm to LLVM as implementation language
<abu[7]>
The intermediate llvm (llvm-ir) is a kind of assembly lang though
<taleon>
A useful step. Maintaining Asselbler programs on the various architectures is not trivial.
<abu[7]>
T
<taleon>
Personally and professionally I use OpenBSD on the server, router, desktop, etc. I will soon try to see if I can get PicoLisp compiled there. PL is currently running under Linux. I have not been able to get it compiled under macos. But I haven't tried any further.
<abu[7]>
There are some docs on running Pil on OpenBSD and MacOS
<taleon>
macos is very special when it comes to includes. I'll have a look at it in a quiet minute. Thanks for pointing out the OpenBSD documentation. That will certainly be helpful.
<abu[7]>
I always forget where it was. But for MacOS there is a hint at the bottom of the picolisp.com start page
<abu[7]>
tankf33der can say more about the two OSes
<taleon>
Yes, that's what I did yesterday. Instead of macports, however, I used brew. llvm version 17.x. However, this is not so important for me at the moment.
<abu[7]>
ok, good
<taleon>
It did not build quickly under OpenBSD. I'll have a look later. https://termbin.com/843e
<taleon>
I probably need to install another shell such as bash.
<taleon>
I will probably have to create corresponding softlinks... Now it's time to take care of lunch. :-)
<abu[7]>
Great, enjoy!
<taleon>
Under OpenBSD, all subsequently installed packages are also installed under `/usr/local/`.
<taleon>
Ok. All llvm-tools can be found under `/usr/local/llvm16/bin`. Now I just have to somehow tell the Makefile to use the tools from this directory.
<taleon>
It was really due to the readline version. I had used the package last, because it didn't work with the source text either.
<abu[7]>
Wow!
<abu[7]>
Congrats :)
<taleon>
Thank you all for the wonderful support. :-) I'm happy now!
<abu[7]>
Great :)
<taleon>
Note to the great OpenBSD guide: wget is not needed. `ftp` from the base system can now also do https.
<taleon>
This saves you having to install a package.
<abu[7]>
ok
<taleon>
Just for the record. Whereby wget is usually installed anyway.
<abu[7]>
I though wget got somehow out of fashion
<abu[7]>
I use curl by default
<taleon>
Yes, I also prefer curl. Above all, curl is interesting for web development to send and receive headers.
<taleon>
I'm not sure what the difference is between readline 8.2 from the source code and readline 8.2 from the OpenBSD packages. However, a few patches are applied that may have an influence. https://github.com/openbsd/ports/tree/master/devel/readline
<abu[7]>
es
<abu[7]>
A bit strange if both are 8.2
<abu[7]>
a new global
<anddam>
taleon: all in all what rl version worked, system's or built-in?
<taleon>
anddam: the source code version from tankf33ders INSTALL.md