| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 3429 - standardize Mu scenarios | Kartik K. Agaram | 2016-09-28 | 1 | -282/+292 |
| | | | | | | | | | | | | | | 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. | ||||
| * | 3396 | Kartik K. Agaram | 2016-09-17 | 1 | -255/+255 |
| | | |||||
| * | 3391 - type abbreviations everywhere | Kartik K. Agaram | 2016-09-17 | 1 | -391/+391 |
| | | | | | | | | | | Well, almost. I can't use them in some places in C++ where I'm just creating a temporary reagent without passing it through transforms. Like in some unit tests. I can't use them in memory-should-contain. And there's one remaining bug: I can't use abbreviations in a couple of places in 075channel.mu. | ||||
| * | 3337 - first use of type abbreviations: text | Kartik K. Agaram | 2016-09-12 | 1 | -58/+58 |
| | | | | | | In the process I've uncover a couple of situations we don't support type abbreviations yet. They're next. | ||||
| * | 2979 | Kartik K. Agaram | 2016-05-19 | 1 | -0/+2100 |