| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
It will always be identical to size_t, just more readable, like
recipe_number, etc. The various unsigned types are sizes, indices (which
often compare with sizes for bounds checking), numbers which are
canonical elements of a specific space (like recipes or mu types), and
ids which I haven't introduced yet.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the process, some extra unit tests as well. The final scenario is newly fixed.
Between the earlier support for '%' escaping C code inside scenarios,
and the previous commit, we now actually have the ability to setup
the Routines data structure just so to simulate different situations.
One unanticipated but happy consequence of ignoring run(""): I can interleave
'+' lines with '-' lines to avoid making any ordering assertions between '+'
lines. So the '+' lines here are checked in order:
+layer1: a
+layer3: c
But here they will pass even if present out of order:
+layer1: a
-layer2: b
+layer3: c
This might be too confusing. In general, relying on run("") is just a temporary
hack. It might well have even worse counter-intuitive effects.
At least I'm not seeing any string-escaping issues so far.
|
| | |
|
| |
|
|
| |
I think I have enough now to port channels over.
|
| |
|
|
|
|
| |
Instead of creating ad hoc data structures for every new state that
routines can be in, track states in one coherent place and provide a
well-defined waypoint for state transitions.
|
| | |
|
| | |
|
| | |
|
|
|
I'm sick of fighting vim's filetype detection. No modeline and files
highlight in random colors. I add a modeline and it stops highlighting
tangle comments. Even though it read my #$%# vimrc! Fuck this shite.
|