about summary refs log tree commit diff stats
path: root/082scenario_screen.cc
Commit message (Collapse)AuthorAgeFilesLines
* 3429 - standardize Mu scenariosKartik K. Agaram2016-09-281-19/+19
| | | | | | | | | | | | | A long-standing problem has been that I couldn't spread code across 'run' blocks because they were separate scopes, so I've ended up making them effectively comments. Running code inside a 'run' block is identical in every way to simply running the code directly. The 'run' block is merely a visual aid to separate setup from the component under test. In the process I've also standardized all Mu scenarios to always run in a local scope, and only use (raw) numeric addresses for values they want to check later.
* 3393Kartik K. Agaram2016-09-171-4/+4
|
* 3390Kartik K. Agaram2016-09-171-2/+2
|
* 3389Kartik K. Agaram2016-09-171-9/+9
|
* 3385Kartik K. Agaram2016-09-171-1/+1
|
* 3379Kartik K. Agaram2016-09-171-18/+18
| | | | Can't use type abbreviations inside 'memory-should-contain'.
* 3374Kartik K. Agaram2016-09-161-2/+2
|
* 3273Kartik K. Agaram2016-08-281-5/+5
| | | | | | | | | | | Undo 3272. The trouble with creating a new section for constants is that there's no good place to order it since constants can be initialized using globals as well as vice versa. And I don't want to add constraints disallowing either side. Instead, a new plan: always declare constants in the Globals section using 'extern const' rather than just 'const', since otherwise constants implicitly have internal linkage (http://stackoverflow.com/questions/14894698/why-does-extern-const-int-n-not-work-as-expected)
* 3272Kartik K. Agaram2016-08-281-3/+3
| | | | | | Move global constants into their own section since we seem to be having trouble linking in 'extern const' variables when manually cleaving mu.cc into separate compilation units.
* 3251Kartik K. Agaram2016-08-251-6/+45
| | | | | Replace some asserts when checking scenario screens with better error messages.
* 3250Kartik K. Agaram2016-08-251-3/+6
|
* 3229 - fake file systems using 'assume-filesystem'Kartik K. Agaram2016-08-201-4/+5
| | | | Built with Stephen Malina.
* 3226Kartik K. Agaram2016-08-181-3/+3
|
* 3178Kartik K. Agaram2016-08-131-0/+5
|
* 3126Kartik K. Agaram2016-07-221-8/+2
|
* 3120Kartik K. Agaram2016-07-211-0/+7
| | | | | | | | Always show instruction before any transforms in error messages. This is likely going to make some errors unclear because they *need* to show the original instruction. But if we don't have tests for those situations did they ever really work?
* 3108Kartik K. Agaram2016-07-101-0/+3
|
* 3025 - fix a minor annoyance in edit/Kartik K. Agaram2016-05-291-3/+1
| | | | | When I floor the down-arrow too much, don't scroll unnecessarily off the bottom of the screen. But *do* scroll if there's errors to show.
* 2983 - migrate buttons over to sandbox/Kartik K. Agaram2016-05-191-0/+1
|
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-241-11/+11
| | | | | | | Now that we no longer have non-shared addresses, we can just always track refcounts for all addresses. Phew!
* 2773 - switch to 'int'Kartik K. Agaram2016-03-131-19/+19
| | | | This should eradicate the issue of 2771.
* 2771 - fix for clang on 32-bit machinesKartik K. Agaram2016-03-131-2/+2
| | | | | | | | | | | Turns out that LLVM/Clang still doesn't support multiplying 64-bit numbers on a 32-bit platform. https://llvm.org/bugs/show_bug.cgi?id=14469 This is just a quick fix, because it turns out I don't have any integer multiplication anywhere else. In the long run I think I'm going to just drop 'long long int' in favor of 'int'. Overflow is less likely than this configuration on somebody's machine.
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-1/+1
| | | | | | | | | | | | I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu.
* 2712Kartik K. Agaram2016-02-261-5/+5
|
* 2709Kartik K. Agaram2016-02-251-1/+0
| | | | | Only Hide_errors when strictly necessary. In other places let test failures directly show the unexpected error.
* 2707Kartik K. Agaram2016-02-251-2/+0
|
* 2581 - make space for the refcount in address:sharedKartik K. Agaram2016-01-201-5/+5
| | | | | | | | | | | We don't yet actually maintain the refcount. That's next. Hardest part of this was debugging the assume-console scenarios in layer 85. That took some detailed manual diffing of traces (because the output of diff was no good). New tracing added in this commit add 8% to .traces LoC. Commented out trace() calls (used during debugging) make that 45%.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-11/+11
| | | | | | | | | | | | | | | | This is the one major refinement on the C programming model I'm planning to introduce in mu. Instead of Rust's menagerie of pointer types and static checking, I want to introduce just one new type, and use it to perform ref-counting at runtime. So far all we're doing is updating new's interface. The actual ref-counting implementation is next. One implication: I might sometimes need duplicate implementations for a recipe with allocated vs vanilla addresses of the same type. So far it seems I can get away with just always passing in allocated addresses; the situations when you want to pass an unallocated address to a recipe should be few and far between.
* 2548 - teach 'print' to print integersKartik K. Agaram2015-12-281-7/+14
| | | | | | | | | | Still can't print non-integer numbers, so this is a bit hacky. The big consequence is that you can't print literal characters anymore because of our rules about how we pick which variant to statically dispatch to. You have to save to a character variable first. Maybe I can add an annotation to literals..
* 2627Kartik K. Agaram2015-12-151-3/+3
|
* 2626Kartik K. Agaram2015-12-151-0/+2
|
* 2468 - overload print-character as just 'print'Kartik K. Agaram2015-11-211-7/+7
|
* 2463 - make edit/ robust to errors in client codeKartik K. Agaram2015-11-191-0/+2
|
* 2430 - make room for more transformsKartik K. Agaram2015-11-131-0/+356