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
*	7867	Kartik K. Agaram	2021-03-07	1	-3/+3
\|
*	7842 - new directory organization	Kartik K. Agaram	2021-03-03	1	-0/+473
	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.

(defpackage #:abs-syn (:use #:openlisp) (:export #:<exp-int> #:<exp-var> #:<exp-str> #:<exp-unr> #:<exp-bin> #:<cmd-rem> #:<cmd-goto> #:<cmd-print> #:<cmd-input> #:<cmd-if> #:<cmd-let> #:<phrase-line> #:<phrase-list> #:<phrase-run> #:<phrase-p-end> #:priority-uop #:priority-binop)) (in-package #:abs-syn) ;; If these were only C enums, without any payload, I'd just use symbols and (error) in the t case. ;; But classes seem better for the associated data, in discriminated unions. (defclass <expression> () () (:abstractp t)) (defclass <exp-int> (<expression>) ((int :accessor int))) (defclass <exp-var> (<expression>) ((var :accessor var))) (defclass <exp-str> (<expression>) ((str :accessor str))) (defclass <exp-unr> (<expression>) ((op :accessor op) (exp :accessor exp))) (defclass <exp-bin> (<expression>) ((exp1 :accessor exp1) (op :accessor op) (exp2 :accessor exp2))) (defclass <command> () () (:abstractp t)) (defclass <cmd-rem> (<command>) ((rem :accessor rem))) (defclass <cmd-goto> (<command>) ((goto :accessor goto))) (defclass <cmd-print> (<command>) ((expr :accessor expr))) (defclass <cmd-input> (<command>) ((var :accessor var))) (defclass <cmd-if> (<command>) ((expr :accessor expr) (num :accessor num))) (defclass <cmd-let> (<command>) ((var :accessor var) (expr :accessor expr))) (defclass <line> () ((num :accessor num) (cmd :accessor cmd))) (defclass <phrase> () () (:abstractp t)) (defclass <phrase-line> (<phrase>) ((line :accessor line))) (defclass <phrase-list> (<phrase>) ()) (defclass <phrase-run> (<phrase>) ()) (defclass <phrase-p-end> (<phrase>) ()) (defun priority-uop (unr-op) (case unr-op ((not) 1) ((uminus) 7))) (defun priority-binop (bin-op) (cond ((member bin-op '(mult div)) 6) ((member bin-op '(plus minus)) 5) ((eql bin-op 'mod) 4) ((member bin-op '(equal less lesseq great greateq diff)) 3) ((member bin-op '(and or)) 2))) (provide "abs-syn")