Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | all apps working again after null get check | Kartik K. Agaram | 2021-05-07 | 2 | -2/+34 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-07 | 2 | -39/+39 | |
| | ||||||
* | always check for null in 'get' instructions | Kartik K. Agaram | 2021-05-07 | 5 | -14/+51 | |
| | ||||||
* | a little bit more information when lookup fails | Kartik K. Agaram | 2021-05-07 | 1 | -1/+31 | |
| | | | | | | Basically this should never, ever happen until I start reclaiming heap memory. I believe the only reason it happens is unprotected writes to address 0 or thereabouts. | |||||
* | an often-overflowing stream when running brcircle | Kartik K. Agaram | 2021-05-07 | 2 | -1/+3 | |
| | | | | We really need to systematically check our trace streams. | |||||
* | . | Kartik K. Agaram | 2021-05-07 | 2 | -6/+8 | |
| | ||||||
* | some boot-time heartbeat messages | Kartik K. Agaram | 2021-05-07 | 2 | -1/+20 | |
| | | | | This will help us with some common debug scenarios. | |||||
* | . | Kartik K. Agaram | 2021-05-07 | 1 | -19/+19 | |
| | ||||||
* | clean up all definitions | Kartik K. Agaram | 2021-05-07 | 1 | -21/+20 | |
| | ||||||
* | clean up chessboard | Kartik K. Agaram | 2021-05-07 | 2 | -11/+15 | |
| | | | | | We still benefit from some helpers here because of the unrolling and multiple calls to helpers. | |||||
* | clean up read_line | Kartik K. Agaram | 2021-05-07 | 1 | -9/+6 | |
| | ||||||
* | clean up Bresenham line-drawing | Kartik K. Agaram | 2021-05-07 | 2 | -26/+54 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-07 | 1 | -6/+6 | |
| | ||||||
* | no, we need hline1 for fill_rect | Kartik K. Agaram | 2021-05-07 | 1 | -8/+10 | |
| | ||||||
* | clean up hline and vline | Kartik K. Agaram | 2021-05-07 | 1 | -10/+10 | |
| | ||||||
* | starting to implement first macros | Kartik K. Agaram | 2021-05-07 | 4 | -0/+20 | |
| | | | | | | | | | | | | | | | Another commit, another bugfix. Some snippets from my currently exploding todo list: - always investigate lookup errors immediately. Beyond the root cause, they should never happen at the moment, while we aren't reclaiming memory. we should always return a more precise error message. Usually involving null pointer checks. - on abort, print out stack trace - emit mapping of labels to addresses during survey - store a mapping of symbols somewhere in the code image - stop allocating 1KB per token; expand space for tokens as needed | |||||
* | give up on nested backquotes for now | Kartik K. Agaram | 2021-05-07 | 2 | -7/+82 | |
| | ||||||
* | macros almost done | Kartik K. Agaram | 2021-05-06 | 1 | -23/+69 | |
| | | | | Just one case left: macros within unquote. | |||||
* | some more cases | Kartik K. Agaram | 2021-05-06 | 1 | -11/+60 | |
| | ||||||
* | first passing test for macroexpand | Kartik K. Agaram | 2021-05-06 | 6 | -41/+249 | |
| | | | | | | | | In the process I spent a long time tracking down a stray TODO in 108write.subx that I thought would abort but didn't since the switch to baremetal. Then after I reintroduced that assertion I had to go track down a bunch of buffer sizes. Stream sizes continue to be a huge mess. | |||||
* | . | Kartik K. Agaram | 2021-05-06 | 1 | -1/+1 | |
| | ||||||
* | more paranoia in shell/globals.mu | Kartik K. Agaram | 2021-05-06 | 1 | -0/+48 | |
| | ||||||
* | shell: macroexpand outermost call | Kartik K. Agaram | 2021-05-06 | 2 | -1/+65 | |
| | ||||||
* | literal macros | Kartik K. Agaram | 2021-05-06 | 1 | -0/+28 | |
| | | | | | | | | | | | Current plan: - some way to define macros. For now: (def f (litmac litfn () (a b) `(+ ,a , b))) - macroexpand will expand calls by passing them through the cdr (f 3 4) macroexpand: ((litfn () (a b) `(+ ,a ,b)) 3 4) => (+ 3 4) eval: (+ 3 4) => 7 | |||||
* | . | Kartik K. Agaram | 2021-05-06 | 1 | -2/+15 | |
| | ||||||
* | back to macros; switch macroexpand to operate in place | Kartik K. Agaram | 2021-05-06 | 2 | -20/+9 | |
| | ||||||
* | belatedly migrate stale example definitions | Kartik K. Agaram | 2021-05-06 | 4 | -93/+99 | |
| | | | | | Also bare-bones syntax highlighting for .limg files. Doesn't work when .limg file is first file opened with Vim. | |||||
* | . | Kartik K. Agaram | 2021-05-06 | 1 | -4/+21 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-04 | 2 | -0/+41 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-04 | 2 | -3/+25 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-04 | 1 | -1/+1 | |
| | ||||||
* | shell: start implementing macros | Kartik K. Agaram | 2021-05-04 | 2 | -1/+7 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-04 | 1 | -6/+6 | |
| | ||||||
* | shell: unquote splice | Kartik K. Agaram | 2021-05-04 | 2 | -1/+121 | |
| | ||||||
* | shell: unquote | Kartik K. Agaram | 2021-05-04 | 1 | -2/+78 | |
| | ||||||
* | shell: start evaluating backquote | Kartik K. Agaram | 2021-05-03 | 1 | -0/+146 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-03 | 1 | -0/+1 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-03 | 1 | -63/+63 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-03 | 1 | -0/+21 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-03 | 1 | -1/+1 | |
| | ||||||
* | reading and printing backquotes and unquotes | Kartik K. Agaram | 2021-05-03 | 3 | -26/+255 | |
| | ||||||
* | printing quoted expressions | Kartik K. Agaram | 2021-05-02 | 1 | -0/+14 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-02 | 1 | -5/+5 | |
| | ||||||
* | . | Kartik Agaram | 2021-05-02 | 1 | -1/+44 | |
| | ||||||
* | . | Kartik Agaram | 2021-05-01 | 21 | -6684/+7950 | |
| | ||||||
* | tool: compute nearby colors in default palette | Kartik K. Agaram | 2021-05-01 | 2 | -1/+235 | |
| | ||||||
* | primitive: convert r/g/b to h/s/l | Kartik K. Agaram | 2021-05-01 | 1 | -0/+234 | |
| | ||||||
* | primitive: read r/g/b for color | Kartik K. Agaram | 2021-05-01 | 2 | -0/+329 | |
| | ||||||
* | . | Kartik K. Agaram | 2021-05-01 | 2 | -4/+4 | |
| | | | | Clean up menus. | |||||
* | cleaner rendering of fake screens and keyboards | Kartik K. Agaram | 2021-05-01 | 2 | -117/+10 | |
| | | | | | | I don't understand why a second line in the keyboard is visible now where it wasn't before. That whole aspect has unclear desires. What exactly do I want to happen on newlines? |