| commit | e6ea92b77539098632d8b310752d75eca9f387f2 | |
| author | elliottcable <me@ell.io> | |
| Tue, 17 May 2011 03:43:49 +0000 (16 23:43 -0400) | ||
| committer | elliottcable <me@ell.io> | |
| Tue, 17 May 2011 03:48:02 +0000 (16 23:48 -0400) | ||
| tree | abd5576d4e75350669e2d1829b709c36d73c335a | treesnapshot (tar.gz zip) |
| parent | 206cdc4654a2996efab1a294ee27846fd4f49b85 | commitdiff |
(- re style) Moving the `initialize` functions into the “family functions” 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.
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.
| Source/Types/fork/fork.c | diffblobblamehistory | |
| Source/Types/fork/ll.c | diffblobblamehistory |