diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2021-11-28 14:57:49 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2021-11-28 15:03:10 -0800 |
commit | 908b2634c6daab8a0d91127044aca1f2daef05bb (patch) | |
tree | 8ef72e4830473651470478df9666a591d149b225 /src/lopcodes.c | |
parent | aed8da775039ed4007eb88a94e27dc58174cc7d0 (diff) | |
download | teliva-908b2634c6daab8a0d91127044aca1f2daef05bb.tar.gz |
split a lumpy abstraction into two cleaner ones
I'm mindful of the way abstractions can create duplicate effort: https://flak.tedunangst.com/post/browser-ktrace-browsing == Kartik's SAD theorem As programs grow complex, you will be repeatedly forced to either: - maintain some State, - perform some computations Again, - or Duplicate some code. Here a small amount of duplication seems like the best alternative. Particularly since no syscalls are involved.
Diffstat (limited to 'src/lopcodes.c')
0 files changed, 0 insertions, 0 deletions