newLISP Fan Club

Hi,

Nothing broke functionally. Rebel keeps the same
language semantics; the changes are primarily in
function naming, not in behavior.

Rebel intentionally diverged to establish a concise,
more Unix/C-like naming for core functions.

There are two straightforward options for existing
newLISP code:

 - Rename function calls to the new Rebel names.
 - Define aliases for the original names.

Both approaches are fully supported and idiomatic.

The authoritative reference is primes.h, which
documents the active Rebel interface and naming.
See the header comment for orientation:

https://github.com/ufko-org/rebel/blob/main/src/primes.h

For renamed functions, the original newLISP name
can usually be inferred from the C primitive name,
which has not changed so far.

For example, new fwrite maps to p_writeFile, meaning
the original function name was write-file.

Regarding GitHub discussions/issues: they were disabled
intentionally to keep development focused.

Ufko

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.

Rebel is no longer newLISP-compatible.
The break is mainly about function naming,
not features.
From here on, Rebel goes its own way.

Ufko.

TL;DR: From now on, set is the only way to assign or
mutate anything in Rebel. There is no separate
set ', setq, setf family.

Thanks for testing, Hapco.

You cloned a short transitional commit where the new
assignment semantics were already in place, but the
explicit error behavior was not yet implemented.

In Rebel, set is now the only assignment primitive.
Internally, set is equivalent to setf.

This means that assignments always operate on places.
Quoted symbols are not accepted as assignment targets.

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

> (set 'a '("hello" "there"))
ERR: quoted symbol used in function set

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

Using (set 'a ...) is rejected by design. Everyone
who uses the (set 'sym ...) syntax in newLISP
has been doing it completely unnecessarily
the whole time.
Current versions emit a clear error in this case.

Until the new assignment semantics are fully documented,
the behavior of set can be considered equivalent to
the existing newLISP setf documentation.

Existing newLISP code that relies on the original
set 'symname, setq, or setf forms must be rewritten to
use the unified set form in order to run on Rebel.

As a temporary migration aid, it is possible to define
an alias for setf or setq, for example in
~/.init.rbl

(constant (global 'setf) set)
(constant (global 'setq) set)

Ufko

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")
>


Best Christmas present ever, exactly what I have wanted for a long time.
And can I just say the wiki is a model of clarity!
Built quickly with no errors and briefly tested on MX-Linux 23.6

Thanks Carlos.
A real hardware test is important information for me!

One note about the current direction:

Rebel removes lambda completely.

If existing code uses lambda* symbols, you need to add your own aliases with
(constant (global ...)) or rewrite the scripts:

lambda is fn
lambda-macro is fn-macro
lambda? is fn?

define returns (fn ...),
define-macro returns (fn-macro ...),
macro returns (fn-macro ... expand ...),
macro? returns true for macros defined with define-macro or macro

Documentation will be updated later.
It is not a priority right now.

Ufko

Quote from: ufko on November 22, 2025, 01:09:15 PMRebel is now fully 64‑bit clean and Unix-native.

For anyone interested in a lean,
Unix-focused swiss-knife interpreter,
this is the version to try

Builds and works fine on macOS 26.1 

That project seems relatively unknown and abandoned afaict

What You say about https://github.com/Solant/rebel/
May be You rename project to any another non-conflicting name.
Your project is very good and needs unique name.