about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 6465Kartik Agaram2020-06-042-0/+2
|
* 6464 - support temporaries in fn output registersKartik Agaram2020-06-042-11/+262
| | | | | | | | The rule: emit spills for a register unless the output is written somewhere in the current block after the current instruction. Including in nested blocks. Let's see if this is right.
* 6463 - clean up some duplicationKartik Agaram2020-06-032-148/+115
| | | | | | Rather than have two ways to decide whether to emit push/pop instructions, just record for each var on the 'vars' stack whether we emitted a push for it, and reuse the decision to emit a pop.
* 6462Kartik Agaram2020-06-032-1/+1
| | | | Stack bug.
* 6461Kartik Agaram2020-06-032-15/+17
|
* 6460Kartik Agaram2020-06-032-7/+6
|
* 6459Kartik Agaram2020-06-032-5/+7
|
* 6458Kartik Agaram2020-06-032-9/+5
|
* 6457 - revert apps/browse.mu to a working stateKartik Agaram2020-06-011-195/+61
|
* 6456 - new directory for live-blogging prototypesKartik Agaram2020-05-3122-0/+2220
| | | | | I don't have layers yet in Mu. But I can still create lots of versions of a program.
* 6455 - abortive second attempt at parsing headingsKartik Agaram2020-05-311-53/+146
| | | | | | | | | | | | | This 'OO' approach seems more scalable, but I need to first wrestle with a parsing issue: this text has a heading: abc *def # ghi* Ugh, so I can't do this translation in a single pass. Then again, maybe I should just keep going and not try to be compatible with GitHub-Flavored Markdown. Require that new headings are also new paragraphs.
* 6454: abortive first attempt at parsing headingsKartik Agaram2020-05-311-3/+41
| | | | | The state machine is already out of control, and I already have bugs like turning '*abc_' into bold text.
* 6453Kartik Agaram2020-05-301-5/+5
|
* 6452Kartik Agaram2020-05-301-6/+7
| | | | Support more than two states.
* 6451Kartik Agaram2020-05-301-2/+6
| | | | Now the trailing asterisk or underscore renders correctly, for starters.
* 6450Kartik Agaram2020-05-301-52/+50
| | | | | The current organization doesn't really work for the next feature (section headings) so let's inline attribute-handling.
* 6449 - italicsKartik Agaram2020-05-301-0/+19
| | | | | | | We're not going to render italics since they still feel like an advanced feature for terminals, and different terminals have different escape sequences for them, and since they often look weird to my eyes on the monospace font of a terminal window. So underscores and italics will both be bold.
* 6448 - markdown for boldKartik Agaram2020-05-301-2/+39
|
* 6447Kartik Agaram2020-05-308-171/+229
|
* 6446Kartik Agaram2020-05-303-99/+89
|
* 6445Kartik Agaram2020-05-301-0/+1
|
* 6444Kartik Agaram2020-05-301-0/+3
|
* 6443Kartik Agaram2020-05-303-311/+488
|
* 6442Kartik Agaram2020-05-302-1/+0
|
* 6441Kartik Agaram2020-05-292-13/+1
| | | | Just always flush Stdout when printing numbers.
* 6440Kartik Agaram2020-05-292-6/+6
| | | | | Minor reordering; the hacky flush-stdout is now only needed if we ever call print-int32-to-screen.
* 6439Kartik Agaram2020-05-292-4/+11
| | | | | Make print-byte less error-prone to use. Now none of our screen primitives are buffered.
* 6438 - multiple pages on screenKartik Agaram2020-05-291-7/+28
| | | | At the moment the number of pages is hard-coded to my screen width.
* 6437 - check screen/window dimensionsKartik Agaram2020-05-292-10/+11
| | | | | | | | This was why I was trying to use a different output register: a second function to call. And I managed to mess it up again, changing the output of load-file, but not how it was computed in the body.
* 6436Kartik Agaram2020-05-291-2/+0
|
* 6435Kartik Agaram2020-05-291-2/+13
|
* 6434Kartik Agaram2020-05-291-3/+3
|
* 6433 - render newlines correctlyKartik Agaram2020-05-292-0/+4
| | | | | | | | | | | | | There were three confounding issues to get past before this seemed to be working right: - row/col count from 1 rather than 0 - I was thinking in decimal rather than hex - print-byte buffers to stdout, but print-string does not. I didn't think this mattered, but it does matter to flush the current line before moving cursor again. Only one of these issues was a bug in the code. The first two were bugs in my mental model that necessitated no changes to code to be corrected.
* 6432 - paginator starting to take shapeKartik Agaram2020-05-291-2/+56
|
* 6431 - Mu function blocks can double as loopsKartik Agaram2020-05-291-7/+5
|
* 6430Kartik Agaram2020-05-291-4/+3
| | | | | Perhaps the lack of safety just forces us to make smaller functions, like Forth.
* 6429Kartik Agaram2020-05-291-0/+35
| | | | | Baby steps. I managed to mess up even this tiny refactoring of print-file.mu. Wish output registers were already checked in calls.
* 6428Kartik Agaram2020-05-291-1/+1
|
* 6427Kartik Agaram2020-05-291-7/+13
|
* 6426Kartik Agaram2020-05-282-32/+44
|
* 6425Kartik Agaram2020-05-285-7654/+7917
|
* 6424Kartik Agaram2020-05-283-1/+2
|
* 6423 - done with sample app 'print-file'Kartik Agaram2020-05-283-6/+35
| | | | | | | | | | | Observations: - the orchestration from 'in' to 'addr-in' to '_in-addr' to 'in-addr' is quite painful. Once to turn a handle into its address, once to turn a handle into the address of its payload, and a third time to switch a variable out of the overloaded 'eax' variable to make room for read-byte-buffered. - I'm starting to use SubX as an escape hatch for features missing in Mu: - access to syscalls (which pass args in registers) - access to global variables
* 6422 - size-of for handlesKartik Agaram2020-05-286-6/+26
|
* 6421Kartik Agaram2020-05-281-0/+0
|
* 6420Kartik Agaram2020-05-281-2/+5
| | | | | | | Starting to feel the need for more static checks, like when I must use a register, or when a variable has been clobbered. The good news: I thought I'd found a bug in apps/mu, but I hadn't.
* 6419 - new primitive for opening filesKartik Agaram2020-05-283-1/+59
|
* 6418Kartik Agaram2020-05-281-2/+14
|
* 6417Kartik Agaram2020-05-281-0/+8
|
* 6416Kartik Agaram2020-05-281-2/+8
|