| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 1276 - make C++ version the default | Kartik K. Agaram | 2015-05-05 | 1 | -1146/+0 |
| | | | | | I've tried to update the Readme, but there are at least a couple of issues. | ||||
| * | 1269 - 'wait-for-routine' | Kartik K. Agaram | 2015-05-05 | 1 | -16/+16 |
| | | |||||
| * | 1267 - 'routine-state' can use the provided routine id | Kartik K. Agaram | 2015-05-05 | 1 | -16/+16 |
| | | |||||
| * | 1247 | Kartik K. Agaram | 2015-05-03 | 1 | -78/+78 |
| | | |||||
| * | 1246 | Kartik K. Agaram | 2015-05-03 | 1 | -129/+129 |
| | | |||||
| * | 1244 | Kartik K. Agaram | 2015-05-03 | 1 | -15/+15 |
| | | |||||
| * | 1242 - simpler implementation for 'scenario' | Kartik K. Agaram | 2015-05-02 | 1 | -17/+258 |
| | | | | | | Also now has the side effect that scenarios can have any number of 'run' or check or any future blocks, in any order. | ||||
| * | 1226 - bugfix in allocating arrays | Kartik K. Agaram | 2015-04-30 | 1 | -348/+348 |
| | | | | | Also our first test of printing to screen. | ||||
| * | 1225 | Kartik K. Agaram | 2015-04-29 | 1 | -0/+127 |
| | | | | | Finally start tracing the actual instructions as they run. | ||||
| * | 1223 - more stable traces for parse scenarios | Kartik K. Agaram | 2015-04-29 | 1 | -14/+14 |
| | | |||||
| * | 1213 | Kartik K. Agaram | 2015-04-28 | 1 | -5/+5 |
| | | |||||
| * | 1206 - 'wait' state for synchronizing routines | Kartik K. Agaram | 2015-04-27 | 1 | -1/+1 |
| | | | | | I think I have enough now to port channels over. | ||||
| * | 1194 | Kartik K. Agaram | 2015-04-24 | 1 | -0/+1 |
| | | |||||
| * | 1193 | Kartik K. Agaram | 2015-04-24 | 1 | -15/+15 |
| | | |||||
| * | 1184 - finally, concurrency | Kartik K. Agaram | 2015-04-24 | 1 | -1/+2 |
| | | |||||
| * | 1168 | Kartik K. Agaram | 2015-04-24 | 1 | -3/+3 |
| | | |||||
| * | 1105 - more primitives for managing ingredients | Kartik K. Agaram | 2015-04-19 | 1 | -1/+1 |
| | | |||||
| * | 1101 | Kartik K. Agaram | 2015-04-19 | 1 | -1/+1 |
| | | |||||
| * | 1097 - 'grow-buffer' works the first time! | Kartik K. Agaram | 2015-04-18 | 1 | -0/+355 |
| | | | | | | | | | | | | | | | | | | | | 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. | ||||
| * | 1090 | Kartik K. Agaram | 2015-04-17 | 1 | -0/+421 |