about summary refs log tree commit diff stats
path: root/400.mu
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik K. Agaram2021-07-161-1/+1
|
* .Kartik K. Agaram2021-07-161-2/+2
|
* initial image renderingKartik K. Agaram2021-07-071-0/+4
| | | | | | Supports just some ASCII formats: https://en.wikipedia.org/wiki/Netpbm Colors are messed up. That's next.
* reading from streamsKartik K. Agaram2021-07-031-0/+1
| | | | | | The Mu shell has no string literals, only streams. No random access, only sequential access. But I've been playing fast and loose with its read pointer until now. Hopefully things are cleaned up now.
* more general timer interfaceKartik K. Agaram2021-06-291-0/+3
|
* snapshotKartik K. Agaram2021-06-201-1/+2
| | | | | This is going better than expected; just 3 failing tests among the new ones.
* flickerlessly render fake screens in environmentKartik K. Agaram2021-06-151-0/+1
| | | | | | | | Font rendering now happens off the real screen, which provides the effect of double-buffering. Apps can now also use convert-graphemes-to-pixels for more traditional double-buffering.
* .Kartik K. Agaram2021-06-081-0/+1
| | | | | | | I wrote a comment about how some code was not covered by tests, and then promptly forgot what it was for. This is why we need tests. Now the hack is gone.
* .Kartik K. Agaram2021-05-291-0/+3
| | | | | Minor counter infrastructure. We invoke next-token 1400 times while loading the shell's data disk, so we're wasting around 1.4MB during tokenization.
* more robust print-cellKartik K. Agaram2021-05-191-0/+4
| | | | | It is used to print to the trace, and we shouldn't crash the whole computer just because the trace ran out of space.
* dump addresses of call stack on abortKartik K. Agaram2021-05-141-0/+1
|
* .Kartik K. Agaram2021-05-141-0/+1
| | | | | Move abort to SubX. We'll need to do some unsafe stuff to display the call stack here.
* primitive: read r/g/b for colorKartik K. Agaram2021-05-011-0/+1
|
* .Kartik K. Agaram2021-04-221-0/+3
|
* shell: separate 'def' from 'set'Kartik K. Agaram2021-04-211-0/+1
| | | | | 'def' creates new bindings (only in globals) 'set' only modifies existing bindings (either in env or globals)
* an interface approximating stack tracesKartik K. Agaram2021-04-201-0/+1
|
* some primitives for monitoring code integrityKartik K. Agaram2021-04-181-0/+4
|
* data.img now has more than one sector of dataKartik K. Agaram2021-04-161-2/+2
|
* explicitly pass data disk to mainKartik K. Agaram2021-03-271-2/+2
|
* mouse support that requires pollingKartik K. Agaram2021-03-231-0/+3
|
* writes to disk now workingKartik K. Agaram2021-03-231-0/+1
| | | | | | Tested by inserting a call into the shell, but we can't leave it in because every test ends up clobbering the disk. So it's now time to think about a testable interface for the disk.
* .Kartik K. Agaram2021-03-221-1/+1
|
* shell: read initial expression from secondary diskKartik K. Agaram2021-03-211-0/+3
| | | | See shell/README.md for (extremely klunky) instructions.
* update vocabulary documentationKartik K. Agaram2021-03-081-3/+3
| | | | Top-level and linux/ now have separate vocabulary.md files.
* 7866Kartik Agaram2021-03-071-3/+3
|
* 7842 - new directory organizationKartik K. Agaram2021-03-031-132/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* 7331 - hacky way to convert slice to stringKartik Agaram2020-12-041-0/+5
|
* 7329 - snapshot: advent day 4 part 2Kartik Agaram2020-12-041-1/+2
| | | | | | | | | | | | I've found two bugs in SubX libraries: 1. next-word had an out-of-bounds read 2. next-word was skipping comments, because that's what I need during bootstrapping. I've created a new variant called next-raw-word that doesn't skip comments. These really need better names. We're now at the point where 4b.mu has the right structure and returns identical result to 4a.mu.
* 7290Kartik Agaram2020-11-271-0/+2
| | | | | | | I've wrestled for a long time with how to support integer division with its hard-coded registers. The answer's always been staring me in the face: just turn it into a function! We already expect function outputs to go to hard-coded registers.
* 7239Kartik Agaram2020-11-151-56/+56
|
* 7225Kartik Agaram2020-11-111-0/+2
| | | | | | | Both manual tests described in commit 7222 now work. To make them work I had to figure out how to copy a file. It requires a dependency on a new syscall: lseek.
* 7127Kartik Agaram2020-10-271-0/+1
|
* 7115Kartik Agaram2020-10-261-2/+2
|
* 7106 - tile: arrays of intsKartik Agaram2020-10-251-1/+1
|
* 7101 - tile: remove quotes when evaluating stringsKartik Agaram2020-10-251-0/+1
| | | | This found several bugs due to me not checking for null strings.
* 7100 - tile: render string literalsKartik Agaram2020-10-251-0/+2
|
* 6963 - tile: more idiomatic conventional replKartik Agaram2020-10-051-1/+1
|
* 6946 - print floats somewhat intuitively in hexKartik Agaram2020-10-041-0/+3
|
* 6921Kartik Agaram2020-10-011-1/+1
|
* 6860Kartik Agaram2020-09-261-0/+1
| | | | | Snapshot: tile currently segfaulting. I need to back up and make it easier to debug.
* 6821 - highlight words clobbered by the next wordKartik Agaram2020-09-201-2/+2
| | | | Another suggestion from the Future of Software forum.
* 6810 - tile: adaptive column widthsKartik Agaram2020-09-191-0/+1
|
* 6808Kartik Agaram2020-09-191-1/+1
|
* 6807 - tile: render intermediate stack stateKartik Agaram2020-09-191-0/+2
|
* 6800Kartik Agaram2020-09-191-2/+2
|
* 6794 - cleaner interface for keyboardKartik Agaram2020-09-161-1/+1
| | | | | | | So far I've been assuming that read-key only works for ascii, and that I'd need to get more sophisticated both for multi-byte utf-8 and multi-byte terminal escape codes like arrow keys. Rather to my surprise, both work fine. We just need to adjust the types to reflect this fact.
* 6792Kartik Agaram2020-09-161-2/+0
| | | | Roll back all buffering of Stdout.
* 6790 experiment: explicit flushKartik Agaram2020-09-161-0/+2
| | | | | | | | | tile is already visibly slow (49x212 screen) :/ So programmer needs more control over performance. But this may not be the right approach. That extra flush-stdout in tui.mu suggests it's either going to be finicky, or we have to flush on every attribute change. And going through a buffered-file may be slower. May.
* 6781 - new app: RPN (postfix) calculatorKartik Agaram2020-09-151-4/+8
| | | | This was surprisingly hard; bugs discovered all over the place.
* 6778Kartik Agaram2020-09-141-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-25 04:37:48 +0000