- Far-left-edge structure-indentation *always* supercedes alignment-indentation (additively, of course) - Taking `…(void);` into account in min-3 calculations. - No longer taking `extern`/`static` keywords into account for min-3 calculations. - A few other, minor, consistency fixes.
…ions” section. Semantically speaking, `initialize()` operates on `struct a_type *`, not `a_type` itself. Until it’s been initialized, it’s not really an object of that type, now is it? Since it doesn’t operate on fully-operational instances of `a_type`, I’m considering them a family function instead of an instance function.
…making `SOMEDAY;` available.
…ning* of `register_Fork()`
…It’s no longer relevant.
- the (new) `->allocate()`, to `malloc()` memory for that type - `->initialize()` to configure basic initial data for that type - `->create()` which calls both, and replaces the old `->allocate()`.
…tion declarations. Turns out a declaration like `struct fork * extern a_func(void)` is illegal, so you have to put the `extern` first. /-:
This also includes the `ll` and `element` structs, and families for all of the above. This code was initially copied from old-world Paws, and subsequently modified massively. I don’t think I’m going to try to do this all in one commit again. I’ll probably directly duplicate old work next time, with an (incomplete) label, and then work towards making it up-to-date, then close the changes with a (complete:) label. This also still includes some old, irrelevant code. The code has been updated to match current style standards, and to compile (and pass the old tests)… and that’s about it. More work to be done here.
…ck has a character in column 1! Again, this seems to break the rules a bit, but I think it looks better.
…s contents are whitespaced.
…er with the typedecl, though.