lysdexic@programming.devM to C++@programming.devEnglish · 3 months agoHow to build highly-debuggable C++ binariesdhashe.comexternal-linkmessage-square1fedilinkarrow-up111arrow-down10cross-posted to: hackernews@lemmy.smeargle.fanscpp@programming.dev
arrow-up111arrow-down1external-linkHow to build highly-debuggable C++ binariesdhashe.comlysdexic@programming.devM to C++@programming.devEnglish · 3 months agomessage-square1fedilinkcross-posted to: hackernews@lemmy.smeargle.fanscpp@programming.dev
minus-square0x0@programming.devlinkfedilinkarrow-up2·3 months ago you have to choose in advance which parts of your binary will be debuggable and which parts of your binary will be fast. Or keep debug code inside an #ifdef. Some nifty tips aside from the general “C++ is bad and obsolete” tone.
Or keep debug code inside an
#ifdef
.Some nifty tips aside from the general “C++ is bad and obsolete” tone.