about summary refs log tree commit diff stats
path: root/081print.mu
Commit message (Collapse)AuthorAgeFilesLines
* 3574Kartik K. Agaram2016-10-231-198/+165
| | | | Shorter branches above longer ones.
* 3429 - standardize Mu scenariosKartik K. Agaram2016-09-281-51/+54
| | | | | | | | | | | | | 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.
* 3390Kartik K. Agaram2016-09-171-23/+23
|
* 3389Kartik K. Agaram2016-09-171-50/+50
|
* 3388Kartik K. Agaram2016-09-171-27/+27
|
* 3385Kartik K. Agaram2016-09-171-69/+69
|
* 3379Kartik K. Agaram2016-09-171-26/+26
| | | | Can't use type abbreviations inside 'memory-should-contain'.
* 3373Kartik K. Agaram2016-09-161-1/+2
| | | | | | Commit 3370 fixed the memory leak but it still had print:character printing characters rather than numbers like it used to before 3365. Go back to the old, unambiguous trace.
* 3341Kartik K. Agaram2016-09-121-1/+1
| | | | | | | Process type abbreviations in function headers. Still a couple of places where doing this causes strange errors. We'll track those down next.
* 3337 - first use of type abbreviations: textKartik K. Agaram2016-09-121-3/+3
| | | | | In the process I've uncover a couple of situations we don't support type abbreviations yet. They're next.
* 3015 - more symbolic names in testsKartik K. Agaram2016-05-261-136/+153
| | | | | | There's still a problem: if I ever want to use any of the special scenario variables like 'screen', 'console', etc., then I can't use 'local-scope' in my scenario.
* 2983 - migrate buttons over to sandbox/Kartik K. Agaram2016-05-191-0/+27
|
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-241-93/+93
| | | | | | | Now that we no longer have non-shared addresses, we can just always track refcounts for all addresses. Phew!
* 2860 - rename 'index-address' to 'put-index'Kartik K. Agaram2016-04-231-6/+6
|
* 2844 - purge get-address from all layersKartik K. Agaram2016-04-161-39/+39
| | | | | Only apps left now, and the wait-for-location uses in the channel primitives.
* 2843 - purge get-address until layer 83Kartik K. Agaram2016-04-161-26/+14
|
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-48/+48
| | | | | | | | | | | | 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.
* 2600 - teach 'print' about addressesKartik K. Agaram2016-01-231-0/+20
| | | | Unfortunate that our type system requires this to be explicit..
* 2586 - show first sandbox with error in statusKartik K. Agaram2016-01-221-0/+1
|
* 2585 - label sandboxes with a numberKartik K. Agaram2016-01-221-1/+13
| | | | | | | | | It also seems useful that the number maps to the name of the file the sandbox is saved in. However this mapping is currently a happy accident and not actually tested. I'm starting to switch gears and help make the editor useable with many many sandboxes. This is just the first step of several.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-92/+92
| | | | | | | | | | | | | | | | 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.
* 2559 - stop using 'next-ingredient' explicitlyKartik K. Agaram2016-01-121-1/+1
| | | | | I still need it in some situations because I have no way to set a non-zero default for an optional ingredient. Open question..
* 2548 - teach 'print' to print integersKartik K. Agaram2015-12-281-50/+76
| | | | | | | | | | 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..
* 2477Kartik K. Agaram2015-11-271-1/+1
|
* 2468 - overload print-character as just 'print'Kartik K. Agaram2015-11-211-28/+28
|
* 2467 - rename 'string' to 'text' everywhereKartik K. Agaram2015-11-211-5/+5
| | | | | | | | Not entirely happy with this. Maybe we'll find a better name. But at least it's an improvement. One part I *am* happy with is renaming string-replace to replace, string-append to append, etc. Overdue, now that we have static dispatch.
* 2460 - headers for remaining recipesKartik K. Agaram2015-11-181-133/+110
|
* 2430 - make room for more transformsKartik K. Agaram2015-11-131-0/+684