| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2026-02-26 | shocking news: leaving shit on stack breaks program | kitty | |
| oops | |||
| 2026-02-26 | use cell+ in s" | kitty | |
| 2026-02-26 | CASE (from jonesforth) | kitty | |
| 2026-02-26 | rename 0branch to ?branch | kitty | |
| 2026-02-26 | comment out for later | kitty | |
| not sure what teh issue is here yet | |||
| 2026-02-26 | fix string stack wonkery? i think? | kitty | |
| i mean it works now afaict... | |||
| 2026-02-26 | don'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-26 | not found error (currently breaks shit) | kitty | |
| 2026-02-26 | add end of input handling to cparse | kitty | |
| 2026-02-26 | handle end of input in PARSE (todo: this in cparse) | kitty | |
| 2026-02-26 | maybe this program is extremely broken. possible | kitty | |
| 2026-02-25 | incomplete assembler displacement | kitty | |
| 2026-02-24 | wtf | kitty | |
| moving the stack after the user memory has entirely fixed the problem i dont understand | |||
| 2026-02-24 | error handling? | kitty | |
| 2026-02-24 | WORDS | kitty | |
| 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-24 | s, (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-23 | i reimplemented s" and it still doesnt work right | kitty | |
| 2026-02-22 | broken, segfaulting .free | kitty | |
| seems to be string handling issue somehow the actual text of the next word ends up on the stack | |||
| 2026-02-22 | move assembler below branching, ?dup | kitty | |
| 2026-02-22 | .REG /digit | kitty | |
| 2026-02-22 | accidentally kept in > | kitty | |
| 2026-02-22 | idea | kitty | |
| the commas for rmmod.reg registers is quite elegant i think. i hope it ends up working well | |||
| 2026-02-22 | starting on assembler | kitty | |
| nothing functional, mostly my comments as i figure all this out | |||
| 2026-02-21 | execute, ? | kitty | |
| 2026-02-21 | hex dpy words, .s in forth! | kitty | |
| 2026-02-21 | .r, fix stack leak | kitty | |
| 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-21 | u.r, fix r> >r | kitty | |
| 2026-02-21 | 1+ 1- | kitty | |
| 2026-02-20 | two spaces for : | kitty | |
| 2026-02-20 | forth83 fwd+backwrd MARK and RESOLVE | kitty | |
| 2026-02-20 | nip, split u. and . into (u.) and (.) intrnl forms | kitty | |
| 2026-02-20 | negate, 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-20 | remove testing stuff | kitty | |
| 2026-02-20 | forth-created pad | kitty | |
| 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. | |||
| 2026-02-19 | rm old unnecessary teststring words | kitty | |
| i still haven't figured out the PNO issue yet. working on it | |||
| 2026-02-19 | recurse, bl, slightly broken PNO | kitty | |
| 2026-02-19 | fucking oops | kitty | |
| 2026-02-18 | fix syntax highlighting (as a treat) | kitty | |
| 2026-02-18 | improve s" | kitty | |
| 2026-02-18 | ." | kitty | |
| 2026-02-18 | litstring + #tib | kitty | |
| 2026-02-18 | add TIB | kitty | |
| 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! | |||
| 2026-02-17 | CHAR | kitty | |
| 2026-02-17 | some notes on DOES> | kitty | |
| 2026-02-17 | variable | kitty | |
| 2026-02-17 | until should be immediate | kitty | |
| 2026-02-17 | else | kitty | |
| 2026-02-16 | jonesforth port improvements of stack words | kitty | |
| 2026-02-16 | port some comparison n logic words from jf | kitty | |
| 2026-02-16 | smudge, rewrite : using create and smudge | kitty | |
 |
index : jewelforth | |
| x86_64 forth |
| summaryrefslogtreecommitdiff |