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

diff options

author	Kartik K. Agaram <vc@akkartik.com>	2021-03-03 22:09:50 -0800
committer	Kartik K. Agaram <vc@akkartik.com>	2021-03-03 22:21:03 -0800
commit	71e4f3812982dba2efb471283d310224e8db363e (patch)
tree	ea111a1acb8b8845dbda39c0e1b4bac1d198143b /apps/ex9
parent	c6b928be29ac8cdb4e4d6e1eaa20420ff03e5a4c (diff)
download	mu-71e4f3812982dba2efb471283d310224e8db363e.tar.gz

7842 - new directory organization

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.

Diffstat (limited to 'apps/ex9')

-rwxr-xr-x

apps/ex9

bin

260 -> 0 bytes

1 files changed, 0 insertions, 0 deletions

" Vim syntax file " Language: mu " Maintainer: Kartik Agaram <mu@akkartik.com> " URL: http://github.com/akkartik/mu " License: public domain " " Copy this into your ftplugin directory, and add the following to your vimrc " or to .vim/ftdetect/mu.vim: " autocmd BufReadPost,BufNewFile *.mu,*.test set filetype=mu let s:save_cpo = &cpo set cpo&vim " todo: why does this periodically lose syntax, like on file reload? " $ vim x.mu " :e "? if exists("b:syntax") "? finish "? endif "? let b:syntax = "mu" setlocal iskeyword=@,48-57,?,!,_,$,- setlocal formatoptions-=t " mu programs have long lines setlocal formatoptions+=c " but comments should still wrap syntax match muComment /#.*$/ | highlight link muComment Comment syntax match muSalientComment /##.*$/ | highlight link muSalientComment SalientComment syntax match muComment /;.*$/ | highlight link muComment Comment syntax match muSalientComment /;;.*$/ | highlight link muSalientComment SalientComment set comments+=n:# syntax match CommentedCode "#? .*" let b:cmt_head = "#? " " mu strings are inside [ ... ] and can span multiple lines " don't match '[' at end of line, that's usually code syntax region muString start=+\[[^\]]+ end=+\]+ syntax match muString "\[\]" highlight link muString String " mu syntax for representing the screen in scenarios syntax region muScreen start=+ \.+ end=+\.$\|$+ highlight link muScreen muString " mu literals syntax match muNumber %[^ ]\+:literal/\?[^ ,]*% syntax match muNumber %\<[0-9-]\?[0-9]\+\>% syntax match muNumber %\<[0-9-]\?[0-9]\+/[^ ,]*% highlight link muNumber Constant syntax match muLabel "^\s\+[^ 0-9a-zA-Z{}#\[\]][^ ]*\s*$" syntax match muLabel %[^ ]\+:label/\?[^ ,]*% syntax match muLabel "<[^ ]*>" highlight link muLabel Constant syntax match muLiteral %[^ ]\+:type/\?[^ ,]*% syntax match muLiteral %[^ ]\+:offset/\?[^ ,]*% syntax match muLiteral %[^ ]\+:variant/\?[^ ,]*% syntax match muLiteral %[^ ]\+:recipe/\?[^ ,]*% highlight link muLiteral Constant syntax keyword muKeyword default-space global-space new-default-space local-scope next-ingredient ingredient | highlight link muKeyword Constant syntax match muDelimiter "[{}]" | highlight link muDelimiter Delimiter syntax match muAssign " <- \|\<raw\>" | highlight link muAssign SpecialChar syntax match muGlobal %[^ ]\+:global/\?[^ ,]*% | highlight link muGlobal SpecialChar syntax keyword muControl reply reply-if reply-unless jump jump-if jump-unless loop loop-if loop-unless break break-if break-unless current-continuation continue-from create-delimited-continuation reply-delimited-continuation | highlight muControl ctermfg=3 " common keywords syntax keyword muRecipe recipe recipe! before after | highlight muRecipe ctermfg=208 syntax keyword muScenario scenario | highlight muScenario ctermfg=34 syntax keyword muData container exclusive-container | highlight muData ctermfg=226 let &cpo = s:save_cpo


context:
space:
mode: