summaryrefslogtreecommitdiff
path: root/jefs.fs
AgeCommit message (Collapse)Author
2026-02-28error handler as :noname wordkitty
2026-02-28octal, :nonamekitty
2026-02-27?comp ?intr (not used yet though)kitty
2026-02-27immediate tick for handler settingkitty
2026-02-27some rearranging, interactive tickkitty
2026-02-27interactivity testkitty
oh that was easy
2026-02-27example: write line from stdin to stdoutkitty
i am unnervingly close to interactive input surprisingly soon
2026-02-27VALUE, and make handler a valuekitty
2026-02-27move syswrite to filehandle areakitty
read-file does not work right now
2026-02-27allot -> allot>, allotkitty
allot> returns an address. allot doesn't
2026-02-27MAKE - it's like create but for arrays and stuffkitty
my create works in a way that makes stuff like `create DATA 8 cells allot` will not work correctly. so i chose a synonym for `create` that works in the correct way.
2026-02-27.errnokitty
i should go to bed
2026-02-27*/mod */ %kitty
2026-02-27z", lowest level file handling, errno stuffkitty
2026-02-27rm old test stuffkitty
2026-02-27fix new handlerkitty
just reset the stack at the error
2026-02-27.rs, rp, also i forgot to reset `say` to use stdoutkitty
2026-02-26folding sectionskitty
figure i'll start doing this now while it's still relatively small
2026-02-26EVALUATE use return stackkitty
2026-02-26shocking news: leaving shit on stack breaks programkitty
oops
2026-02-26use cell+ in s"kitty
2026-02-26CASE (from jonesforth)kitty
2026-02-26rename 0branch to ?branchkitty
2026-02-26comment out for laterkitty
not sure what teh issue is here yet
2026-02-26fix string stack wonkery? i think?kitty
i mean it works now afaict...
2026-02-26don't interpret "kitty
also fixes the Leaving shit on the stack issue. i still dont know what that's about but i just `drop` it and its fixed
2026-02-26not found error (currently breaks shit)kitty
2026-02-26handle end of input in PARSE (todo: this in cparse)kitty
2026-02-26maybe this program is extremely broken. possiblekitty
2026-02-25incomplete assembler displacementkitty
2026-02-24wtfkitty
moving the stack after the user memory has entirely fixed the problem i dont understand
2026-02-24error handling?kitty
2026-02-24WORDSkitty
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.
2026-02-24s, (cmove, in forth)kitty
still doesn't work. i'm still at a loss for where the problem is coming from. i think i will make it use cmove, again, and put a breakpoint there so i can figure out how uninterpreted code is making it into the stack.
2026-02-23i reimplemented s" and it still doesnt work rightkitty
2026-02-22broken, segfaulting .freekitty
seems to be string handling issue somehow the actual text of the next word ends up on the stack
2026-02-22move assembler below branching, ?dupkitty
2026-02-22.REG /digitkitty
2026-02-22accidentally kept in >kitty
2026-02-22ideakitty
the commas for rmmod.reg registers is quite elegant i think. i hope it ends up working well
2026-02-22starting on assemblerkitty
nothing functional, mostly my comments as i figure all this out
2026-02-21execute, ?kitty
2026-02-21hex dpy words, .s in forth!kitty
2026-02-21.r, fix stack leakkitty
i forgot i yoinked my ALLOT from jonesforth which returns a value. may change this but it would require a few rewrites so eh
2026-02-21u.r, fix r> >rkitty
2026-02-20two spaces for :kitty
2026-02-20forth83 fwd+backwrd MARK and RESOLVEkitty
2026-02-20nip, split u. and . into (u.) and (.) intrnl formskitty
2026-02-20negate, abs, tuck from pforth, .kitty
holby Sheet!! numeric i/o is real!!! need to test different bases. if hex works and also if number padding works (i have not tested that yet) i can start writing better debugging tools and i can stop having to pipe my output through xxd!! this also will mean the end of DONEDONEYIPPEEEE,,,, :<
2026-02-20remove testing stuffkitty