Chris to Programmer Humor@programming.devEnglish · 2 months agoUnexplained Phenomenas3.us-east-005.backblazeb2.comimagemessage-square25fedilinkarrow-up1793arrow-down14file-text
arrow-up1789arrow-down1imageUnexplained Phenomenas3.us-east-005.backblazeb2.comChris to Programmer Humor@programming.devEnglish · 2 months agomessage-square25fedilinkfile-text
minus-squarenogooduser@lemmy.worldlinkfedilinkEnglisharrow-up12·2 months agoI used to work on an old DOS product and we didn’t have a debugger so we used to have a DEBUG command line argument with if (DEBUG) printf(“debugging”); to try to see what was happening and the number of times that code alone fixed the problem was scary.
minus-squarepsycho_driver@lemmy.worldlinkfedilinkarrow-up5·2 months agoI mean . . . I still do this on my own stuff. If I’m interested in optimizing for speed I’ll do it as #ifdef instead of if ()
I used to work on an old DOS product and we didn’t have a debugger so we used to have a DEBUG command line argument with
if (DEBUG) printf(“debugging”);to try to see what was happening and the number of times that code alone fixed the problem was scary.
I mean . . . I still do this on my own stuff. If I’m interested in optimizing for speed I’ll do it as #ifdef instead of if ()