| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Again quite ugly. There's an increasing amount of state here, particularly
the interplay between headers and soft newlines.
|
| | |
|
| |
|
|
|
| |
I'm not bothering with this for bold regions just yet. Might need rethinking,
given how ugly this is.
|
| | |
|
| | |
|
| |
|
|
| |
Ooh, it's nice and composable if we just never render the delimiters. Perfect.
|
| |
|
|
|
|
| |
The state machines are still not composing perfectly. The initial asterisk
gets added in one, and the trailing asterisk in another. I suppose "always
render the terminator" is fairly regular.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Fix a stray copy-paste when deciding whether to emit spills for registers
(commit 6464).
|
| |
|
|
| |
Fix CI.
|
| |
|
|
|
|
|
| |
I had a little "optimization" to avoid creating nested blocks if "they weren't
needed". Except, of course, they were. Lose the optimization. Sometimes
we create multiple jumps when a single one would suffice. Ignore that for
now.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
No, we can stay with the previous prototype a little longer.
|
| |
|
|
|
|
| |
Let's start committing new prototype directories *before* we start hacking
on them. Version control is useful right from the draft when programming
in a language without any error messages.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
Stack bug.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I don't have layers yet in Mu. But I can still create lots of versions
of a program.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
The state machine is already out of control, and I already have bugs like
turning '*abc_' into bold text.
|
| | |
|
| |
|
|
| |
Support more than two states.
|
| |
|
|
| |
Now the trailing asterisk or underscore renders correctly, for starters.
|
| |
|
|
|
| |
The current organization doesn't really work for the next feature (section
headings) so let's inline attribute-handling.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|