jewelforth - x86

Age	Commit message (Collapse)	Author
3 days	source-id	kitty

3 days	cmove>	kitty

3 days	... whooops	kitty

3 days	NOT, duskos-based rename h0 > herestart hend > heremax	kitty

3 days	rename: allot> → allot@	kitty
	also based on duskos names
3 days	rename :noname to :>	kitty
	the name :> is taken from dusk os. i like it and it's shorter than :noname and i don't care about standard compliance
3 days	error handler as :noname word	kitty

3 days	octal, :noname	kitty

4 days	?comp ?intr (not used yet though)	kitty

4 days	immediate tick for handler setting	kitty

4 days	some rearranging, interactive tick	kitty

4 days	interactivity test	kitty
	oh that was easy
4 days	example: write line from stdin to stdout	kitty
	i am unnervingly close to interactive input surprisingly soon
4 days	VALUE, and make handler a value	kitty

4 days	move syswrite to filehandle area	kitty
	read-file does not work right now
4 days	allot -> allot>, allot	kitty
	allot> returns an address. allot doesn't
4 days	MAKE - it's like create but for arrays and stuff	kitty
	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.
5 days	.errno	kitty
	i should go to bed
5 days	/mod / %	kitty

5 days	z", lowest level file handling, errno stuff	kitty

5 days	rm old test stuff	kitty

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