Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | . | Kartik Agaram | 2021-05-31 | 1 | -17/+19 |
| | | | | State as of https://archive.org/details/akkartik-mu-2021-05-31 | ||||
* | . | Kartik K. Agaram | 2021-05-31 | 1 | -3/+3 |
| | |||||
* | data.limg now loading properly again | Kartik K. Agaram | 2021-05-31 | 1 | -1/+1 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-22 | 1 | -1/+1 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-19 | 1 | -2/+2 |
| | |||||
* | shell: roll back a change to the 'when' macro | Kartik K. Agaram | 2021-05-15 | 1 | -2/+2 |
| | | | | | Introduced in commit 1adc904ef3 from a week ago, but it turns out brcircle has been consistently broken ever since. | ||||
* | A 'bowboard', a chessboard of rainbow circles | Kartik K. Agaram | 2021-05-08 | 1 | -23/+31 |
| | | | | Compare with (chessboard screen 256) | ||||
* | a full-circle rainbow | Kartik K. Agaram | 2021-05-08 | 1 | -2/+29 |
| | |||||
* | new shell macro: do | Kartik K. Agaram | 2021-05-07 | 1 | -2/+3 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-07 | 1 | -3/+5 |
| | |||||
* | . | 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 | 1 | -10/+12 |
| | | | | | 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 | 1 | -26/+22 |
| | |||||
* | 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 | 1 | -0/+4 |
| | | | | | | | | | | | | | | | 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 | ||||
* | belatedly migrate stale example definitions | Kartik K. Agaram | 2021-05-06 | 1 | -91/+91 |
| | | | | | Also bare-bones syntax highlighting for .limg files. Doesn't work when .limg file is first file opened with Vim. | ||||
* | bresenham circles | Kartik K. Agaram | 2021-04-25 | 1 | -1/+22 |
| | | | | Known issue: circles of radius 9 crash. (Multiples of 9 overflow the trace.) | ||||
* | bug in bresenham lines | Kartik K. Agaram | 2021-04-25 | 1 | -2/+2 |
| | |||||
* | shell: primitives 'and' and 'or' | Kartik K. Agaram | 2021-04-25 | 1 | -11/+1 |
| | |||||
* | . | Kartik K. Agaram | 2021-04-25 | 1 | -0/+84 |