jewelforth - x86

Age	Commit message (Collapse)	Author
5 days	fix new handler	kitty
	just reset the stack at the error
5 days	.rs, rp, also i forgot to reset `say` to use stdout	kitty

5 days	folding sections	kitty
	figure i'll start doing this now while it's still relatively small
5 days	EVALUATE use return stack	kitty

5 days	shocking news: leaving shit on stack breaks program	kitty
	oops
5 days	use cell+ in s"	kitty

5 days	CASE (from jonesforth)	kitty

5 days	rename 0branch to ?branch	kitty

5 days	comment out for later	kitty
	not sure what teh issue is here yet
5 days	fix string stack wonkery? i think?	kitty
	i mean it works now afaict...
5 days	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
5 days	not found error (currently breaks shit)	kitty

5 days	handle end of input in PARSE (todo: this in cparse)	kitty

5 days	maybe this program is extremely broken. possible	kitty

7 days	incomplete assembler displacement	kitty

7 days	wtf	kitty
	moving the stack after the user memory has entirely fixed the problem i dont understand
7 days	error handling?	kitty

7 days	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.
8 days	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.
8 days	i reimplemented s" and it still doesnt work right	kitty

9 days	broken, segfaulting .free	kitty
	seems to be string handling issue somehow the actual text of the next word ends up on the stack
9 days	move assembler below branching, ?dup	kitty

9 days	.REG /digit	kitty

9 days	accidentally kept in >	kitty

9 days	idea	kitty
	the commas for rmmod.reg registers is quite elegant i think. i hope it ends up working well
9 days	starting on assembler	kitty
	nothing functional, mostly my comments as i figure all this out
10 days	execute, ?	kitty

11 days	hex dpy words, .s in forth!	kitty

11 days	.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
11 days	u.r, fix r> >r	kitty

11 days	two spaces for :	kitty

11 days	forth83 fwd+backwrd MARK and RESOLVE	kitty

12 days	nip, split u. and . into (u.) and (.) intrnl forms	kitty

12 days	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,,,, :<
12 days	remove testing stuff	kitty

12 days	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.
12 days	rm old unnecessary teststring words	kitty
	i still haven't figured out the PNO issue yet. working on it
12 days	recurse, bl, slightly broken PNO	kitty

13 days	fix syntax highlighting (as a treat)	kitty

13 days	improve s"	kitty

13 days	."	kitty

13 days	litstring + #tib	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	CREATE asm word	kitty
	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	+! -! allot	kitty

2026-02-15	improve number	kitty
	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!