mu - Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society.

	Commit message (Collapse)	Author	Age	Files	Lines
*	1702 - experiment: start using 'ordinal' in names	Kartik K. Agaram	2015-07-04	1	-7/+7
\| \| \| \| \| \| \|	It comes up pretty early in the codebase, but hopefully won't come up in the mu level until we get to higher-order recipes. Potentially intimidating name, but such prime real estate with no confusing overloadings in other projects!
*	1585	Kartik K. Agaram	2015-06-17	1	-1/+1
\|
*	1417 - draft zoom levels in traces	Kartik K. Agaram	2015-05-21	1	-2/+2
\|
*	1401 - shave 80% off chessboard test time	Kartik K. Agaram	2015-05-18	1	-0/+13
\| \| \| \|	It was all going to laboriously writing out 300+ MB to disk.
*	1391 - avoid unsigned integers	Kartik K. Agaram	2015-05-17	1	-2/+2
\|
*	1365	Kartik K. Agaram	2015-05-13	1	-11/+4
\|
*	1357 - temporarily revert floating-point support	Kartik K. Agaram	2015-05-12	1	-1/+1
\|
*	1356 - snapshot #2: floating point support	Kartik K. Agaram	2015-05-12	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	I added one test to check that divide can return a float, then hacked at the rippling failures across the entire entire codebase until all tests pass. Now I need to look at the changes I made and see if there's a system to them, identify other places that I missed, and figure out the best way to cover all cases. I also need to show real rather than encoded values in the traces, but I can't use value() inside reagent methods because of the name clash with the member variable. So let's take a snapshot before we attempt any refactoring. This was non-trivial to get right. Even if I convince myself that I've gotten it right, I might back this all out if I can't easily persuade others that I've gotten it right.
*	1344	Kartik K. Agaram	2015-05-11	1	-0/+10
\|
*	1323 - keyboard supports backspace and newline	Kartik K. Agaram	2015-05-10	1	-3/+13
\| \| \| \| \| \|	Lots mixed into this commit: some off-by-one errors in display.cc a new transform to translate jump labels that I'd somehow never gotten around to supporting
*	1308	Kartik K. Agaram	2015-05-08	1	-0/+10
\|
*	1298 - better ingredient/product handling	Kartik K. Agaram	2015-05-07	1	-10/+12
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	All primitives now always write to all their products. If a product is not used that's fine, but if an instruction seems to expect too many products mu will complain. In the process, many primitives can operate on more than two ingredients where it seems intuitive. You can add or divide more than two numbers together, copy or negate multiple corresponding locations, etc. There's one remaining bit of ugliness. Some instructions like get/get-address, index/index-address, wait-for-location, these can unnecessarily load values from memory when they don't need to. Useful vim commands: %s/ingredients\[$[^\]]$\]/ingredients.at(\1)/gc %s/products\[$[^\]]$\]/products.at(\1)/gc .,$s/\[$.$]/.at(\1)/gc
*	1276 - make C++ version the default	Kartik K. Agaram	2015-05-05	1	-0/+52
	I've tried to update the Readme, but there are at least a couple of issues.