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
*	1601	Kartik K. Agaram	2015-06-19	1	-2/+6
\|
*	1597 - port more helpers from arc version	Kartik K. Agaram	2015-06-19	1	-0/+10
\|
*	1595	Kartik K. Agaram	2015-06-18	1	-1/+1
\|
*	1585	Kartik K. Agaram	2015-06-17	1	-3/+3
\|
*	1514 - cleaner way to show backspaces in fake keyboard	Kartik K. Agaram	2015-05-30	1	-3/+38
\| \| \| \|	In the process we now support unicode in all mu strings!
*	1458	Kartik K. Agaram	2015-05-25	1	-4/+17
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	While pushing out color support in fake screens I realized I've been complecting the special-case of a special-case to transform literal-string arguments for 'new'. As a result I hadn't been catching bad habits like giving its arg the wrong type. Now we have cleaner separation of the two variants of 'new', a few more checks, and better error messages when we mis-call it. Aside: I've added a third goto target. Sliding into spaghetti? Keep an eye on it. This goto might become a common pattern: a layer hooking into a previous one to prevent it from happening. In this case new on literal-strings prevents the transform for new from triggering.
*	1417 - draft zoom levels in traces	Kartik K. Agaram	2015-05-21	1	-5/+5
\|
*	1414 - traces now robust to new recipes/types	Kartik K. Agaram	2015-05-21	1	-3/+1
\|
*	1391 - avoid unsigned integers	Kartik K. Agaram	2015-05-17	1	-14/+14
\|
*	1385	Kartik K. Agaram	2015-05-16	1	-1/+2
\|
*	1379 - avoid all uninitialized-memory issues	Kartik K. Agaram	2015-05-15	1	-1/+13
\|
*	1363 - rename 'integer' to 'number'	Kartik K. Agaram	2015-05-13	1	-14/+14
\| \| \| \|	..now that we support non-integers.
*	1357 - temporarily revert floating-point support	Kartik K. Agaram	2015-05-12	1	-7/+4
\|
*	1356 - snapshot #2: floating point support	Kartik K. Agaram	2015-05-12	1	-4/+7
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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.
*	1318 - 1317 actually works now	Kartik K. Agaram	2015-05-10	1	-0/+6
\|
*	1298 - better ingredient/product handling	Kartik K. Agaram	2015-05-07	1	-30/+49
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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/+157
	I've tried to update the Readme, but there are at least a couple of issues.