Commit 2b4642bd9ea97662688f72f67c8b785e1230e4b0 - Oxcart

Small edit. Chris Pressey 5 years ago

1 changed file(s) with 8 addition(s) and 8 deletion(s). Raw diff Collapse all Expand all

-8

README.md less more

309	309	almost as if concatenating the program symbols results in a program
310	310	structured like this:
311	311
312		S→:→0→^→%→■
313
314		where each → is a continuation, and execution happens by executing an
315		instruction, then just following the attached continuation arrow to get
316		the next thing to execute. An instruction like `S` has the effect of
317		pushing the arrow (and, virtually, everything that follows it) onto
318		the stack, and an instruction like `%` does have an arrow attached to
319		it, but that arrow is ignored — an arrow popped off the stack is used
	312	S → : → 0 → ^ → % → ■
	313
	314	where each → is a continuation, and ■ is HALT, and execution happens by
	315	executing an instruction, then just following the attached continuation
	316	arrow to get the next thing to execute. An instruction like `S` has the
	317	effect of pushing the arrow (and, virtually, everything that follows it)
	318	onto the stack, and an instruction like `%` does have an arrow attached
	319	to it, but that arrow is ignored — an arrow popped off the stack is used
320	320	instead.
321	321
322	322	But one implication of this is that an Oxcart program can't access