13/ well, at least you know that none of the implicit casts lose any significant bits, or mangles sign bits into data bits, or vice versa, right, because the compiler warns in those cases? no, because that compiler warning has been turned off
-
Show this thread
-
14/ well, ok, hopping back, at least you can use function signatures to help you understand things, right? no, because
#defines ah, right, you said that...ok, so rewrite those as functions no, because any one given#define is applied to arguments of MULTIPLE DIFFERENT TYPES1 reply 0 retweets 13 likesShow this thread -
15/ so, anyway, a few weeks later: * I've commented all of the code * I've renamed several funcs * I've rewritten macros as funcs * I've renamed variables * I've turned on compiler warnings * I've written funcs to do safe casts (or crash with error if values forbid it) >>>
4 replies 0 retweets 11 likesShow this thread -
16/ ...and I've narrowed down a memory corruption issue to about a 5 line block. whew. Thank God this is F̶r̶i̶ whiskey-day
1 reply 0 retweets 18 likesShow this thread -
17/ Anyway, gig is scheduled to run another ~4 weeks and I'm laying 50/50 odds that they won't renew me because I'm incompetent. ¯\_(ツ)_/¯
4 replies 0 retweets 14 likesShow this thread -
Replying to @MorlockP
You know, for someone whose mission statement was "make a computer from scratch that can be trusted not to be broken like all the other computers in existence" he sure wrote a lot of untrustable broken code
1 reply 0 retweets 3 likes -
Replying to @random_eddie @MorlockP
... although to be fair I'm sure it's broken in ways UNLIKE all the other computers in existence
1 reply 0 retweets 2 likes -
Replying to @random_eddie
something terrible is about to enter our world https://www.youtube.com/watch?v=a4TPo8eYEs0 …
3 replies 0 retweets 2 likes -
Replying to @MorlockP
The difference is Ivo wasn't very good at raising venture capital
1 reply 0 retweets 1 like -
we don't conduct our rituals up on the roof; we do them in left pasture
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.