newLISP Fan Club

Still, we have the source code, and people who appreciate newlisp, so it's not really gone because the site is. I briefly tried Janet, and may again, but at the time it just didn't do it for me. Too many dots, square brackets, and random punctuation. And what's wrong with lists? Not a list to be found...

Ok, I apologize. I did say it was no big deal and I never said anything about losing me a a potential user. I'll continue to follow your project with interest and look forward to seeing what you can make of it.

Thanks, your post made it seem more drastic.

Just for the sake of discussion, though, I think I prefer write-file and append-file to fwrite and fappend. the latter might be more concise, but they are less expressive and not as natural to type. No biggie though. :-)

Hi ufko,

What broke? Will any modification of existing newlisp code allow it to run in rebel?

https://github.com/ufko-org/rebel/discussions gets a 404, btw.

Yes, this is (potentially) great!

There is this, though:

Rebel v1.0 64-bit on Linux IPv4/6 UTF-8 libffi, options: rebel -h

> (set 'a '("hello" "there"))
("hello" "there")
> a
nil
>


newLISP v.10.7.6 64-bit on Linux IPv4/6 UTF-8 libffi, options: newlisp -h

> (set 'a '("hello" "there"))
("hello" "there")
> a
("hello" "there")
>


Hi guys,

How can we attract attention to newlisp from folks who recognize its worth and have the skills to maintain and improve it? Maybe fork it and re-write it in Nim, Go, or Rust? If we went that direction it might get people from those communities interested. We could name the fork Nimlisp, or something.

What do you think?