f2c5b05374
6611 - start adding to common vocabulary in Mu
2020-07-05 10:41:41 -07:00
cf28645f8a
6610 - tweak the Linux boot image generator
...
So far we hardcoded the translation process and it only supported SubX.
Now we pass in an ELF binary and outsource how it's generated.
2020-07-05 10:38:18 -07:00
ff856aa0ba
6609
2020-07-05 08:19:00 -07:00
b5984ac5b6
6607 - new prototype dir for spreadsheet ideas
2020-07-05 08:15:07 -07:00
f33979aab1
6606
2020-07-02 15:22:14 -07:00
d99a870a11
6605
2020-07-01 20:48:45 -07:00
996402e8fd
6604 - new app
...
https://archive.org/details/akkartik-2min-2020-07-01
In the process I found a bug, added a new syscall, and 'emulated' it.
2020-07-01 16:47:20 -07:00
792451d1be
6603
2020-06-30 14:59:45 -07:00
2655a4a91d
6602
2020-06-30 14:54:30 -07:00
8bd3c2b5a8
6601
2020-06-29 19:21:43 -07:00
6c7f7abdb8
6600
2020-06-29 19:16:36 -07:00
222548962c
6599
2020-06-29 19:14:19 -07:00
12e2b93a4b
6598
2020-06-29 18:35:20 -07:00
59cf3ae983
6597
2020-06-29 18:33:52 -07:00
1afc882890
6596
2020-06-29 18:31:17 -07:00
690fa191f1
6595
2020-06-29 18:01:44 -07:00
05dabd816a
6594 - start standardizing the meaning of 'print'
2020-06-29 17:58:01 -07:00
40323d3388
6593
2020-06-28 23:36:26 -07:00
8ce50909c4
6592 - error-checking for integer stmts feels done
2020-06-28 23:25:18 -07:00
9483fdc1fb
6591
2020-06-28 23:17:34 -07:00
4ddc2620f7
6590
2020-06-28 23:10:45 -07:00
896e3bcfb2
6589
2020-06-28 23:09:10 -07:00
d31bd529f7
6588
2020-06-28 18:49:50 -07:00
52d3ee0326
6587
2020-06-28 14:35:45 -07:00
f7a174c2a1
6586 - error-checking for 'get' stmts feels done
2020-06-28 14:23:31 -07:00
1a89b13b9c
6585
2020-06-28 11:50:50 -07:00
bf4fbab76d
6584
2020-06-28 10:19:02 -07:00
60bffdaa49
6583
2020-06-28 09:53:32 -07:00
76a669f689
6582
2020-06-28 09:10:16 -07:00
fbc4544ff8
6581
2020-06-28 08:49:08 -07:00
e98a6babb5
6580
2020-06-28 08:25:37 -07:00
f58a6acc3f
6579
2020-06-28 00:55:31 -07:00
1da16dd6cb
6578 - redo error if 'get' on unknown field
...
This commit reimplements commit 6515 to happen during type-checking rather
than as early as possible. That way we naturally get a more informative
error message.
2020-06-27 21:03:43 -07:00
ab42709e14
6577
2020-06-27 14:30:07 -07:00
14d9b56668
6576
2020-06-27 14:23:50 -07:00
ca9dec80b6
6575
2020-06-27 12:13:43 -07:00
a39d96444b
6574
2020-06-27 11:47:36 -07:00
3a558d22ec
6573
2020-06-21 23:29:46 -07:00
3b02c3dfa2
6572
...
Small change to mu.subx to keep the treeshaker working with it. That's
currently the only place where we prevent jumps across 'functions'.
2020-06-21 17:31:38 -07:00
47fe226b7e
6571
2020-06-21 17:13:21 -07:00
6bfb565819
6570 - error on use of a clobbered var
...
All tests now passing, and factorial.mu and all other apps now working.
The new checks caught one problem in a few prototypes.
2020-06-21 17:08:03 -07:00
6883b8d1c7
6569 - correct the second failing test
2020-06-21 16:53:44 -07:00
c50303cc63
6568
2020-06-21 14:58:14 -07:00
b38d54c402
6567
2020-06-21 14:56:25 -07:00
056858ddd9
6566 - improve some error messages
...
I need to pass the function around to fix the failing test; might as well
fix the error messages while I'm at it.
2020-06-21 14:46:08 -07:00
85eb816725
6565 - support tmux in control mode
...
https://github.com/tmux/tmux/wiki/Control-Mode
https://www.iterm2.com/documentation-tmux-integration.html
2020-06-21 14:08:30 -07:00
8d40bf6705
6564 - second failing test
2020-06-21 11:57:48 -07:00
4efc921811
6563
...
The desire captured by a test is often hard to verbalize, path-dependent
and more fertile for the future than its original impulse. On some level,
someone wanting to rip out features has to just ask for each scenario,
"what do I want to happen here?" And nobody's gonna do that. At best, somebody
may be trying to rip out some complex feature, and run into some collateral
damage around the edges that they have to inspect more closely. "Do I care
about preserving this behavior?"
2020-06-21 11:54:11 -07:00
c70beadc7a
6562
...
The new failing test is now passing, and so is this manual test that had
been throwing a spurious error:
fn foo {
var a/eax: int <- copy 0
var b/ebx: int <- copy 0
{
var a1/eax: int <- copy 0
var b1/ebx: int <- copy a1
}
b <- copy a
}
However, factorial.mu is still throwing a spurious error.
Some history on this commit's fix: When I moved stack-location tracking
out of the parsing phase (commit 6116, Mar 10) I thoughtlessly moved block-depth
tracking as well. And the reason that happened: I'd somehow gotten by without
ever cleaning up vars from a block during parsing. For all my tests, this
is a troubling sign that I'm not testing enough.
The good news: clean-up-blocks works perfectly during parsing.
2020-06-21 11:06:25 -07:00
19fea2b6a2
6561 - failing test
...
Test `test-shadow-name-2` shows that we aren't popping off more than one
variable from each block that we exit.
2020-06-21 10:33:23 -07:00
Kartik Agaram