Denial

lisp-leanstack.png A third stack with one-byte return tags has been introduced to jump around inside the evaluator instead of having it call itself. That doubled the number of recursions before the CPU stack is running out. The "problem" are the built-in functions that call the evaluator....

Performance has been upped by 40%. The CPU stack use has also been halved almost. Doing recursions is actually a bad thing at the moment. :( That's the perfect opportunity to turn beautiful code (c'mon I'm using cool-retro-term) into a trigger for panic. But I'll head out for sun light and ice cream...

After loading "env.lisp" there's now a REPL. You'll drop back to the top-level on errors.
Added all targets (c64, c128, plus4, vic20) to the archive.

lisp-blocktest.png The VIC brightening the day running this for three minutes: (var c 10000) (fn block-test () (out "Looping...")(terpri) (block nil tag (setq c (-- c)) (? (== 0 (% c 100)) (& (print c) (terpri))) (? (not (== c 0)) (go 'tag)))) (block-test) It *is* slow, no question ab...

Some progress with the Lisp: * Garbage collector passes stress tests (HOT!) Impressed by myself the code size increased a bit. ;p * Symbols are also strings. READ won't do look-ups for re-use when they are double quoted. * Function LOAD to include files is working and can be nested (up to three time...

I went too far down the source tree for too long, missing that that stuff in the README is already older than a Unix beard. Objective: build an OS for "home computers" with banked memory expansion (VIC first ;)) that actually has practical use, is self-sufficient and will last by being ope...

Just shining some light on a potentially symbiotic project :) It took me three hours to assemble an answer. So much for my state of mind at the moment. External cause. Whatever brings you joy! Really just a matter of if you prefer to devote your hours to writing Vi or the OS. I haven't used Vi65 in...

Are you aware of Soci's vi65 ? I don't think the source is currently available (and I dunno if Soci would be open to sharing it), which, as a tool, makes it kind of a deal breaker for me. Nonetheless, might be worth looking into depending on how much time you want to sink into editor development. I...

Screenshot from 2024-05-20 10-11-38.png I'd like to be able to switch between the unnamed VI clone and the yet unnamed Lisp interpreter. "VIC VI" is unbelievably worse than "VIC-20" spoken in German and before naming things: why waste time baptizing along when it's in the TUNIX ...

Et voilà. Compacting mark-and-sweep GC with relocation and low memory needs. Here's the code: https://github.com/SvenMichaelKlose/tunix/blob/master/src/lib/lisp/gc.c I like it. Symbol look-ups of READ take ages with a full heap. That's bad. Also bad: in the end there'll be no more than 24K heap and ...

The 40x24 char terminal had to go. It's still a 10K binary (cc65-compiled).

tokra wrote: ↑Sat May 18, 2024 7:05 am These parameters are explained when starting xvic -? or xvic -help

Thanks!

lisp-1+1.png With implementing the built-ins the question is what movie to watch for soft entertainment. After a stomach-churning week (which isn't over yet) completing the GC isn't very inviting. The GC should always work as long as there're three free bytes on the heap. Source codes: https://gith...

Yes. How the flipping heck is that done? With
all other files get filtered out. Wanne be a little bit daring, you know.