newLISP Fan Club

Quote from: marchildmann on August 07, 2023, 07:51:56 AMThank you Greg for managing the new forums!
Just re-registered because my previous nickname "hilti" was taken.

Cheers
Marc

Welcome back @marchildmann!

FYI your previous username should still belong to you. Try resetting the password for that username. If you still have control over that email you should get an email letting your reset it.

Thank you Greg for managing the new forums!
Just re-registered because my previous nickname "hilti" was taken.

Cheers
Marc

Quote from: iacore on July 31, 2023, 01:21:52 AMI have fixed some bugs of newLISP here: https://git.envs.net/iacore/newerlisp
I also added `(write-expr x)`. May you find this useful.

Have you considered putting out some release notes? Feel free to take inspiration from how Lutz does it or create your own method (e.g. a simple `HISTORY.md` file is often useful).

I have fixed some bugs of newLISP here: https://git.envs.net/iacore/newlisp
I also added `(write-expr x)`. May you find this useful.

I know there's a `newlispdoc` utility that creates documentation based on code comments. I'm not sure if that's used to build the full manual though.

Yeah we need someone to act as an active maintainer who can continue the newLISP spirit / way of doing things.

Editng the HTML file manually doesn't seem to work well for development. Does anyone have the raw data extracted from the HTML manual?

This seems to be how newLISP works

On 64-bit systems, try the following in REPL.

(+ -9223372036854775808 -1)

(+ 9223372036854775807 1)

Luckly, this is caught with UBSan.

You can see the details of this bug in the README of https://codeberg.org/iacore/newerlisp


P.S. does anyone know an existing fork of newLISP?

There seems to be a repo at https://github.com/kosh04/newlisp