about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1106Kartik K. Agaram2015-04-201-1/+1
|
* 1105 - more primitives for managing ingredientsKartik K. Agaram2015-04-1933-50/+164
|
* 1104 - support 'dump' in mu scenariosKartik K. Agaram2015-04-191-4/+7
|
* 1103Kartik K. Agaram2015-04-192-0/+32
|
* 1102Kartik K. Agaram2015-04-192-0/+23
|
* 1101Kartik K. Agaram2015-04-1917-56/+57
|
* 1100Kartik K. Agaram2015-04-192-0/+829
|
* 1099 - new recipe: convert integer to decimal stringKartik K. Agaram2015-04-1810-14/+1292
|
* vim highlighting for labelsKartik K. Agaram2015-04-181-1/+2
|
* 1097 - 'grow-buffer' works the first time!Kartik K. Agaram2015-04-182-0/+372
| | | | | | | | | | | | | | | | | | | I thought I'd need to duplicate scenarios to simulate running some code, making some checks, running some more code. But I can just keep saving state to raw locations! I'd still have to manage raw locations myself, though. And it can be ping-pongy to have to check on the other blocks then go back to the run block. But what's the alternative? Multiple run blocks (even excluding the implementation effort) raise questions of namespace sharing across them. If it gets too bad I can intersperse recipes inside the scenario. Yes, that will work. Of course, overly long tests might themselves be a bad idea. We'll see, this is all terra incognita syntactically speaking. This might not be enough to check that a routine is waiting on a channel, but should keep us until then. Wait, even there what you need is a way to check on the status of your child routines. Yeah, doable. Even if we're getting ahead of ourselves.
* 1096Kartik K. Agaram2015-04-185-5/+5
|
* 1095Kartik K. Agaram2015-04-181-0/+1
|
* 1094 - demarcate sections in layersKartik K. Agaram2015-04-1712-27/+46
| | | | | | We have tangled vs regular comments, but they highlight the same. So we're still at 3 colors for comments. Anything more starts to seem gratuitous.
* 1093 - little more vim support for the old arc versionKartik K. Agaram2015-04-172-0/+10
|
* 1092 - vim: auto-insert tangle comments like regular onesKartik K. Agaram2015-04-171-0/+3
|
* 1091Kartik K. Agaram2015-04-172-18/+17
|
* 1090Kartik K. Agaram2015-04-179-20/+684
|
* 1089Kartik K. Agaram2015-04-172-0/+71
|
* 1088 - start porting the 'buffer' typeKartik K. Agaram2015-04-175-1/+230
|
* 1087 - mu files can now define containers and exclusive containersKartik K. Agaram2015-04-174-1/+102
|
* 1086 - support variant names in 'maybe-convert'Kartik K. Agaram2015-04-172-3/+63
|
* 1085 - to access variants of sum types use 'maybe-convert'Kartik K. Agaram2015-04-174-1/+111
|
* 1084Kartik K. Agaram2015-04-1730-51/+56
|
* 1083 - start of a sum type for muKartik K. Agaram2015-04-173-0/+89
|
* 1082Kartik K. Agaram2015-04-173-11/+10
| | | | | Turns out I'm only able to define a 'raise' macro because I have include no system headers after that point.
* 1081Kartik K. Agaram2015-04-171-1/+1
|
* 1080Kartik K. Agaram2015-04-171-1/+1
|
* 1079Kartik K. Agaram2015-04-171-0/+1
|
* 1078 - better line numbersKartik K. Agaram2015-04-173-1/+25
| | | | Skip tangle comments inside tangle rather than in the makefile.
* 1077Kartik K. Agaram2015-04-1721-16/+49
|
* 1076Kartik K. Agaram2015-04-171-2/+5
|
* 1075Kartik K. Agaram2015-04-1768-174/+157
|
* 1074Kartik K. Agaram2015-04-1731-52/+52
|
* 1073 - stop fixing the values of primitive recipesKartik K. Agaram2015-04-1714-163/+102
| | | | | In the process I give up trace stability when I move files around, but I gain in exchange the ability to move files around.
* 1072Kartik K. Agaram2015-04-1720-0/+0
|
* 1071Kartik K. Agaram2015-04-161-0/+0
|
* 1070Kartik K. Agaram2015-04-161-0/+4
|
* 1069 - rename record/field to container/elementKartik K. Agaram2015-04-1612-48/+61
| | | | | | | | | This seems more obvious to laypeople. I've also come up with a design for sum types: I'm going to call them exclusive containers. You call 'get' on containers, 'index' on arrays, and 'maybe-convert' on exclusive containers (as well as tagged types, but that's even later).
* 1068 - better line numbersKartik K. Agaram2015-04-152-9/+90
| | | | | Line numbers were broken after inserting some lines from elsewhere. Now we add a #line directive not just before the lines but also after.
* 1067 - no need to indent methods anymoreKartik K. Agaram2015-04-152-51/+50
|
* 1066 - bugfix: support string literals with colonsKartik K. Agaram2015-04-155-13/+38
|
* 1065 - example program for closuresKartik K. Agaram2015-04-142-3/+35
|
* 1064 - rough support for correct line numbers in error messagesKartik K. Agaram2015-04-142-0/+42
|
* 1063 - variable names for surrounding spaces now workKartik K. Agaram2015-04-1420-22/+326
| | | | This was a pain to debug.
* 1062 - bugfix: wasn't aliasing Current_routineKartik K. Agaram2015-04-145-14/+15
| | | | You can't write tests for stupidity.
* 1061Kartik K. Agaram2015-04-142-0/+28
|
* 1060Kartik K. Agaram2015-04-142-6/+5
|
* 1059Kartik K. Agaram2015-04-131-0/+6
|
* 1058 - scenarios can now check traceKartik K. Agaram2015-04-126-0/+160
|
* 1057Kartik K. Agaram2015-04-122-8/+10
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-23 12:10:37 +0000