https://github.com/BartGo/forth-atari is a collection of Forth code snippets - some are mine but most come from Forth Dimensions or other magazines of the era. Those which finally work were tested with APX Extended #figforth (by Patrick Mullarky) on #atari8bit, emulated in Altirra... Especially dev tools are interesting - finding all words which use a specified word (!); decompiling; breakpoints; screen-based editing... Behold, #forth is the ultimate puzzle langauge, the pinnacle of recreational computing...
GitHub - BartGo/forth-atari: Programs and code snippets for APX Extended Fig-Forth

Programs and code snippets for APX Extended Fig-Forth - BartGo/forth-atari

GitHub

CODE RP@
XSAVE STX,
TSX, TXA, PHA,
1 # LDA,
XSAVE LDX,
PUSH JMP,

Thanks to this single #6502asm #forth word (which adds access to the current return stack pointer, to APX #figforth on #atari8bit) - Forth can do better debugging, tracing, logging, errors can show all the way down (up?) the return stack to better identify the source of an error... Forth Dimensions published so many great articles in the 80s! Another revolutionary invention is a "yield" (r> r> swap >r >r) / "coroutine".

I'm figuring out how to load software in the #Robotron #Z1013. I found a useful feature in #jkcemu to store the data into a wav file.
Now the #CasDuino is finally being used in a meaningful way. And voila, the #FigForth with a size of approx. 10kByte starts without any problems. It's significantly faster than the TinyBasic from the Robotron cassette ;)
#RetroComputing #Forth #Z80CPU
RP@ seems to be generally unavailable for ALL #figforth #forth on #atari8bit. Why, FIG? Such a weapon in my hands would be only used for a greater good! Manuals and books mention it, Forth Dimensions has examples (unclear for which platform though) but I see no RP@ or anything allowing accessing current return stack pointer address. I also understand that later #forth standards further reduced access to the most exciting words... I am angry now! Same about R0 word!