Denial

Orangeman96 wrote: ↑Wed Jun 12, 2024 5:04 pm

pixel wrote: ↑Tue Jun 11, 2024 8:45 pm [...] Almost had an accident in my underwear [...]

Too funny! -OGM

Dynamic scope has its traps as symbols may get shadowed in... shadowy places. Lexical scope is far too CPU-intensive. Clashes can be avoided by having arguments renamed automatically but that's not essential by now.

MACROEXPAND and QUASIQUOTE work but there are GC issues. Almost had an accident in my underwear, thinking it was all for nothing. So much for the inflationary use of the word "shame". Instead, we're almost there. A working Lisp interpreter on the VIC isn't too much to be ashamed of. Howeve...

Hello, I've tried to join the Git repo and to create a folder where to insert my contribute, but didn't manage. It mentions something like I do need to push access to the repository. Sorry, I am not a developer. Just a funboy. Most devs seem to carry their spine upside down, so I guess fun boys are...

I've set up a Git repo and called the thing "TEAM DINO" as it's supposed to be a team effort all the way. And those copyright issues which shouldn't be any more. :( https://github.com/SvenMichaelKlose/team-dino EDIT: I put the sprite code of ARUKANOIDO in which I ported halfway to ca65 – a...

Just shining some light on a potentially symbiotic project :) I'm in with my latest sprite code which, I've heard, brings record-breaking performance and I want a blindfold before some shouts "FIRE!". Using a generalized sprite library for what's planned will give disappointing results. I...

Am almost done with macro expansion. Added user-defined special forms: functions whose arguments aren't evaluated, e.g. for QUASIQUOTE. Had to add the +3K area to have some heap left. The VIC allows for a neat optimization that boosts performance but we're not interested in optimizing yet, are we? :...

Screenshot from 2024-06-10 19-47-46.png Trigger. Flashback. Horror in all colours. Should you still be disappointed about no release: Finishing move on bastard neighbor #2 tomorrow. For the record: I just destroyed some coke dealer's (also to juveniles) life and business. Now that that hardcore dep...

This nightly build *yawn!* fixes a lot of bugs only early releases have to offer. I/O works much better.

EDIT: Some more bug fixes plus some macro- and quasiquote-expansion code.

I checked with the doctor ("C'mooon! At least some weed!?") but it still looks doable to bring on the C compiler natively on the VIC. How could I possibly arrive at that conclusion? Well, here's the size of the "tré" Lisp transpiler which can compile down to assembly level (with ...

Am bringing that truck load of retro stuff people say would be mine back home. Found some moments to inline the BLOCK special form and most built-ins use a generalized type checker for their arguments. Performance dropped to 03:40 for the BLOCK-TEST (32-bit signed integer numbers now). MAKE-COUNT ma...

I've added target 'unix' (it even makes a d64 image for it which is of course nonsense). The Lisp runs on it and the VI is probably next to become Linux-terminal compatible. Had trouble with the stack-optimization for built-ins and some elephant in the room. With no optimization a gcc'ed Lisp is 350...

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.