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
*	rename grapheme to code-point-utf8	Kartik K. Agaram	2021-11-09	2	-108/+108
\| \| \| \| \| \|	Longer name, but it doesn't lie. We have no data structure right now for combining multiple code points. And it makes no sense for the notion of a grapheme to conflate its Unicode encoding.
*	7846	Kartik K. Agaram	2021-03-04	1	-1/+2
\|
*	7842 - new directory organization	Kartik K. Agaram	2021-03-03	4	-0/+1078
	Baremetal is now the default build target and therefore has its sources at the top-level. Baremetal programs build using the phase-2 Mu toolchain that requires a Linux kernel. This phase-2 codebase which used to be at the top-level is now under the linux/ directory. Finally, the phase-2 toolchain, while self-hosting, has a way to bootstrap from a C implementation, which is now stored in linux/bootstrap. The bootstrap C implementation uses some literate programming tools that are now in linux/bootstrap/tools. So the whole thing has gotten inverted. Each directory should build one artifact and include the main sources (along with standard library). Tools used for building it are relegated to sub-directories, even though those tools are often useful in their own right, and have had lots of interesting programs written using them. A couple of things have gotten dropped in this process: - I had old ways to run on just a Linux kernel, or with a Soso kernel. No more. - I had some old tooling for running a single test at the cursor. I haven't used that lately. Maybe I'll bring it back one day. The reorg isn't done yet. Still to do: - redo documentation everywhere. All the README files, all other markdown, particularly vocabulary.md. - clean up how-to-run comments at the start of programs everywhere - rethink what to do with the html/ directory. Do we even want to keep supporting it? In spite of these shortcomings, all the scripts at the top-level, linux/ and linux/bootstrap are working. The names of the scripts also feel reasonable. This is a good milestone to take stock at.

/* Test file for minus operator spacing functionality */ /* This tests the new spacing-based ambiguity resolution for minus operator */ ..out "=== Minus Operator Spacing Tests ==="; /* Basic unary minus tests */ test1 : -5; test2 : -3.14; test3 : -10; test4 : -42; /* Basic binary minus tests */ test5 : 5 - 3; test6 : 10 - 5; test7 : 15 - 7; test8 : 10 - 2.5; /* Legacy syntax tests (should continue to work) */ test9 : (-5); test10 : (-3.14); test11 : (-10); test12 : 5-3; test13 : 15-7; /* Complex negative expressions */ test14 : -10 - -100; test15 : -5 - -3; test16 : -20 - -30; /* Assertions to validate behavior */ ..assert test1 = -5; /* Unary minus: -5 */ ..assert test2 = -3.14; /* Unary minus: -3.14 */ ..assert test3 = -10; /* Unary minus: -10 */ ..assert test4 = -42; /* Unary minus: -42 */ ..assert test5 = 2; /* Binary minus: 5 - 3 = 2 */ ..assert test6 = 5; /* Binary minus: 10 - 5 = 5 */ ..assert test7 = 8; /* Binary minus: 15 - 7 = 8 */ ..assert test8 = 7.5; /* Binary minus: 10 - 2.5 = 7.5 */ ..assert test9 = -5; /* Legacy: (-5) = -5 */ ..assert test10 = -3.14; /* Legacy: (-3.14) = -3.14 */ ..assert test11 = -10; /* Legacy: (-10) = -10 */ ..assert test12 = 2; /* Legacy: 5-3 = 2 */ ..assert test13 = 8; /* Legacy: 15-7 = 8 */ ..assert test14 = 90; /* Complex: -10 - -100 = 90 */ ..assert test15 = -2; /* Complex: -5 - -3 = -2 */ ..assert test16 = 10; /* Complex: -20 - -30 = 10 */ ..out "=== Basic Minus Operator Spacing Tests Passed ===";