yab-- (yabmm or yab minus minus) is an experimental version of the yab programming language with ncurses compiled back in - hence the name. I see yab-- as installable alongside regular yab. It will have its own IDE and it's own help system.
Once that is up and running, we'll start adding other new features, either within yab-- itself or within a standard libraries setup. When it comes out of development, it may be distributed under a different name (yab++ ? 😃 ).
You will be able to run yab-- programs as scripts, and you will still be able to bind them to the yabmm binary, but I am dropping the pseudo-compilation of the Buildfactory. That was a great idea back when it allowed you to create a standalone program that didn't require yab to be installed on the user's computer. But now every program requires libyab.so (or in this case, libyabmm.so) even if bound or built, so what is the point?
I've been playing around with various other BASIC dialects - I was just reluctant to fork yab. But I'm not seeing any movement on yab. One particularly irritating thing is that ncurses support was removed "because of licensing conflict". But ncurses and yab are both on extremely liberal licenses. If you don't want yab to be used to make CLI programs, that's fine, but then IMHO don't leave the ncurses-dependent commands littering the documentation for year after year. So the first step is to get that ncurses functionality back.
Some years ago I published a handbook for yab. I intend to revisit this and use it as the basis for the yab-- documentation.
Find my progress on Codeberg. Yes, the LLM involvement is minimal ATM, but it will increase and is documented. I am daring them to kick me off 😁 .
