• Joined on 2025-03-02
simon commented on issue simon/post-scarcity#9 2026-03-19 14:25:31 +00:00
The bignum bug(s)

If, as proposed, in 0.1.0 I implement bignums in Lisp, there's a beautiful and easy-to-understand explanation of how they're implemented in ulisp here, which will…

simon pushed tag release/0.0.6 to simon/post-scarcity 2026-03-19 14:20:40 +00:00
simon pushed to develop at simon/post-scarcity 2026-03-19 14:00:42 +00:00
99d4794f3b Upversioned the C source tree to '0.0.7-SNAPSHOT', but proposing to start experimental
simon pushed to master at simon/post-scarcity 2026-03-19 13:50:39 +00:00
e5e0de957c Release 0.0.6!
788cb48b37 Ready for release 0.0.6 (still lots of bugs).
a20c956288 'Fixed' issue #8; but done so by introducing a goto. Not entirely happy about this.
dc5cac0bd8 Work on the 'member?' bug - (issue #8) -- which turns out to be assoc/interned.
7d0ce67373 Fixed a segfault when the system can initialise no more pages.
Compare 64 commits »
simon pushed to develop at simon/post-scarcity 2026-03-19 13:39:59 +00:00
788cb48b37 Ready for release 0.0.6 (still lots of bugs).
simon closed issue simon/post-scarcity#11 2026-03-18 21:37:40 +00:00
The member? bug
simon pushed to develop at simon/post-scarcity 2026-03-18 21:37:10 +00:00
a20c956288 'Fixed' issue #8; but done so by introducing a goto. Not entirely happy about this.
simon pushed to develop at simon/post-scarcity 2026-03-18 20:45:26 +00:00
dc5cac0bd8 Work on the 'member?' bug - (issue #8) -- which turns out to be assoc/interned.
simon commented on issue simon/post-scarcity#11 2026-03-18 16:37:49 +00:00
The member? bug

This is in commit #7d0ce67373, although the bug has certainly been present in all commits up to this one.

simon opened issue simon/post-scarcity#11 2026-03-18 16:35:29 +00:00
The member? bug
simon pushed to develop at simon/post-scarcity 2026-03-18 13:31:26 +00:00
7d0ce67373 Fixed a segfault when the system can initialise no more pages.
simon pushed to develop at simon/post-scarcity 2026-03-18 12:22:56 +00:00
69b199fecd Found and fixed a bug I did not previously know about in println.
54a99b6796 Working on the member? bug. No fix, but some improvements in debug message format.
Compare 2 commits »
simon pushed to develop at simon/post-scarcity 2026-03-16 15:28:33 +00:00
109d400f00 Added the unit test for member!
simon pushed to develop at simon/post-scarcity 2026-03-16 15:27:06 +00:00
de50a30be2 Getting closer to tracking down the member bug, but cannot use debugger on laptop screen.
simon pushed to develop at simon/post-scarcity 2026-03-14 21:29:49 +00:00
d42ece5711 Tactical commit while working on the bignum bug, AGAIN.
simon commented on issue simon/post-scarcity#9 2026-03-14 21:25:12 +00:00
The bignum bug(s)

H'mmm... 0.0.5 also gets that wrong, but differently.

:: (+
    10000000000000000000
    10000000000000000000
    10000000000000000000
    10000000000000000000
    1000000000000000
simon commented on issue simon/post-scarcity#9 2026-03-14 21:19:43 +00:00
The bignum bug(s)

There is also a bug in add that's definitely a regression:

:: (set! i
  (+
    10000000000000000000
    10000000000000000000
    10000000000000000000
    10000000000000000000
 
simon commented on issue simon/post-scarcity#9 2026-03-14 21:15:51 +00:00
The bignum bug(s)

However, in 0.0.6, multiply is definitely wrong:

:: (* 1152921504606846975 2)

1
:: (inspect (* 1152921504606846975 2))

        INTR (1381256777) at page 7, offset 945 count
simon commented on issue simon/post-scarcity#9 2026-03-14 21:12:40 +00:00
The bignum bug(s)

OK, I'm now working in the 0.0.6 branch. There are certainly regressions, but I think the problems are more in print than in add.

:: 1152921504606846977

2
:: (inspect
simon pushed to develop at simon/post-scarcity 2026-03-14 19:27:52 +00:00
7f34601523 Well, that was easy! Stack limit now working.