summaryrefslogtreecommitdiff
path: root/jefs.s
AgeCommit message (Collapse)Author
5 daysmaybe this program is extremely broken. possiblekitty
7 daysincomplete assembler displacementkitty
7 dayswtfkitty
moving the stack after the user memory has entirely fixed the problem i dont understand
7 dayserror handling?kitty
7 daysWORDSkitty
still not sure whats going on with s". i have discovered that using multiple s" seems to point the LFA of cell+ (the first forth-defined word) to directly after the text of the second string. now i just need to figure out Why or How that could possibly be happening.
8 daysi reimplemented s" and it still doesnt work rightkitty
11 dayshex dpy words, .s in forth!kitty
11 daysu.r, fix r> >rkitty
11 days1+ 1-kitty
12 daysforth-created padkitty
for some reason a separate PAD section wasn't working. this also fixes the 18 digit Issue. there are still issues i need to sort out though.
12 daysrm old unnecessary teststring wordskitty
i still haven't figured out the PNO issue yet. working on it
13 daysfucking oopskitty
13 dayslitstring + #tibkitty
13 daysadd TIBkitty
realising that my plan of just Rewriting everything in forth later was a little Silly, and i can just create a TIB variable and use initfile as its initial value. probably should also create a #TIB variable and make the interpreter (or parse?) use it. i think this makes an EVALUATE word (idk if that was what it was called?) possible too which means file reading and input from terminal would also be possible. wonderful!
14 daysCHARkitty
2026-02-17elsekitty
2026-02-16jonesforth port improvements of stack wordskitty
2026-02-16port some comparison n logic words from jfkitty
2026-02-16smudge, rewrite : using create and smudgekitty
2026-02-16CREATE asm wordkitty
i Probably should change : to use this. and while i'm at it make a word for setting/unsetting the smudge bit.
2026-02-16+! -! allotkitty
2026-02-16tab is whitespacekitty
2026-02-15improve numberkitty
i think that doing Everything in forth while possible is kinda putting more effort in for no reason, so we now have BASE and the ability to use hex digits. whee!
2026-02-15emit, cr, spkitty
2026-02-14[compile] and 'kitty
2026-02-140branch (untested)kitty
2026-02-14branch!!kitty
2026-02-14immediate, /mod, *kitty
2026-02-14makefile fix, arithmetickitty
2026-02-14it works???????????????kitty
2026-02-13backslash commentskitty
2026-02-13,,, *maybe* working?kitty
2026-02-13fix STATEkitty
2026-02-13move HERE to .bss properkitty
i don't know how to mark the heap as executable. im not entirely sure it's possible. we can't increase its size with this but it Works. compiling mode still doesn't work though... the code in `test` runs in interpreting mode.
2026-02-13a shitload of temporary testing stuff+stack fixkitty
compiling is fucked still interpreting is fixed (no longer leaves its debris on the stack)
2026-02-09stackwords, number in interpreterkitty
gonna have to enter the debugging mines soon
2026-02-09NUMBER and LIT (untested)kitty
2026-02-09immediate interpreter, :, untestedkitty
2026-02-09reverse order in interpreterkitty
i could maybe test this at some point, but maybe it's a little more efficient. who knows
2026-02-09compile/interpret in interpreterkitty
2026-02-08oopskitty
2026-02-08; compiling a ret and setting to interpretingkitty
2026-02-08COMPILE,kitty
maybe will not work because of endianness but it will be a simple fix
2026-02-08expand brk and assign it as HEREkitty
2026-02-08state variable + macroskitty
2026-02-08separate >cfa into a wordkitty
2026-02-08initfile BYE workingkitty
2026-02-08i believe it now passes PARSEkitty
2026-02-08almost certainly deeply broken FINDkitty
x86 assembly is fucked
2026-01-30put a redundant null byte after the stringkitty
this will cause issues if the word has a null byte in the name. so don't do that. obviously