about summary refs log tree commit diff stats
path: root/tangle.mu
Commit message (Collapse)AuthorAgeFilesLines
* 578 - switch to non-polymorphic 'print' functionsKartik K. Agaram2015-01-171-1/+1
| | | | | Also clean up various prints from last few commits. As a convention, for debugging we always print directly to host.
* 574 - printing string literals is a hack; hard-code it in for nowKartik K. Agaram2015-01-161-2/+2
|
* 571 - screen primitives take an explicit terminalKartik K. Agaram2015-01-151-3/+3
| | | | | | | | | | | | | | | | | This will let me swap in a fake in tests. Still hacky, though. I'm sure I'm not managing the parameter right in the chessboard app. And then there's the question of whether it should also appear as an output operand. But it's a start. And using nil to mean 'real' is a reasonable convention. If I ever need to handle multiple screens perhaps we'll have to switch to 1:literal/terminal and 2:literal/terminal, etc. But those are equally easy to guard on.
* 497 - strengthen the concept of 'space'Kartik K. Agaram2015-01-021-1/+1
| | | | | | | | | | | | | | | | | | | | 'default-scope' is now 'default-space' 'closure-generator' is now 'next-space-generator' The connection to high-level syntax for closures is now tenuous, so we'll call the 'outer scope' the 'next space'. So, let's try to create a few sentences with all these related ideas: Names map to addresses offset from a default-space when it's provided. Spaces can be strung together. The zeroth variable points to the next space, the one that is accessed when a variable has /space:1. To map a name to an address in the next space, you need to know what function generated that space. A corollary is that the space passed in to a function should always be generated by a single function. Spaces can be used to construct lexical scopes and objects.
* 428 - cleanup odds and endsKartik K. Agaram2014-12-141-13/+13
|
* 403 - 'function' is more clear than 'def'Kartik K. Agaram2014-12-121-2/+2
|
* 401 - stop abbreviating opsKartik K. Agaram2014-12-121-4/+4
| | | | | We expect users to come across mu from arbitrary bits of code, so try to make each line as self-contained as possible.
* 321 - before/after can now come anywhereKartik K. Agaram2014-11-241-24/+9
| | | | | | This pollutes our traces with all 'system software'. Too much trouble to keep it out; just lump it for now. Who knows, might even be useful. Most of the time convert* labels are easy to grep out when debugging.
* 319 - ack, forgot to handle blocks when tanglingKartik K. Agaram2014-11-241-0/+50
Will the 'lightweight tools' really be all that useable if we encourage people to layer them one atop another and track precisely what inputs each can accept? Something to keep an eye on. In the meanwhile, we have a new (but very unrealistic) example demonstrating the tangling directives. There's still a big constraint on ordering: before/after clauses have to come before functions that need them.