JPDev@programming.dev to Programmer Humor@programming.dev · 9 months agoifn'tprogramming.devimagemessage-square3fedilinkarrow-up13arrow-down10
arrow-up13arrow-down1imageifn'tprogramming.devJPDev@programming.dev to Programmer Humor@programming.dev · 9 months agomessage-square3fedilink
minus-squareTrailblazing Braille Taser@lemmy.dbzer0.comlinkfedilinkarrow-up2·9 months agoI propose a new, more threatening kind of control flow. do { /* something */ } or else { /* you don't want to find out */ }
minus-squaregex@lemmy.worldlinkfedilinkarrow-up2·9 months agoSome C++ style guides suggest the following naming convention for functions that crash on any error OpenFileOrDie()
I propose a new, more threatening kind of control flow.
do { /* something */ } or else { /* you don't want to find out */ }
Some C++ style guides suggest the following naming convention for functions that crash on any error
OpenFileOrDie()