sanitation@lemmy.radio to Programming@programming.dev · 2 days agoBjarne Stroustrup: How do I deal with memory leaks? By writing code that doesn't have any.www.stroustrup.comexternal-linkmessage-square22linkfedilinkarrow-up182arrow-down19file-text
arrow-up173arrow-down1external-linkBjarne Stroustrup: How do I deal with memory leaks? By writing code that doesn't have any.www.stroustrup.comsanitation@lemmy.radio to Programming@programming.dev · 2 days agomessage-square22linkfedilinkfile-text
minus-squareavocado@programming.devlinkfedilinkarrow-up3arrow-down3·24 hours agoC++'s so called smarter mechanisms are ugly af. I would rather my RAM crash and burn than use its standard library.
minus-squarechunes@lemmy.worldlinkfedilinkarrow-up4·24 hours agoyeah. I’d rather use C and statically allocate everything up front, even if that’s not a great fit
minus-squaresobchak@programming.devlinkfedilinkarrow-up2·17 hours agoWhen I did embedded programming that’s what I did. Nothing was dynamically allocated. It also allowed me to write a debugger that would watch how variables changed by just directly reading from memory, chart them, and and stuff like that.
C++'s so called smarter mechanisms are ugly af. I would rather my RAM crash and burn than use its standard library.
yeah. I’d rather use C and statically allocate everything up front, even if that’s not a great fit
When I did embedded programming that’s what I did. Nothing was dynamically allocated. It also allowed me to write a debugger that would watch how variables changed by just directly reading from memory, chart them, and and stuff like that.