Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I absolutely agree, I've written a few hundred thousand loc of C++ at this point and I don't remember one time where I felt that having RAII was anything but great. It made me absolutely hate whenever I had to work in other languages Java and C# and had to remember to release non-memory resources manually.


That’s basically any gced language and the fix is present for decades at this point: try-with-resources, ‘using’, ‘with’ (with-whatever IIRC can be traced back to Lisp…)


no, those are absolutely not fixes: you have to remember to use "using", "with", etc. whereas you have to go out of your way to circumvent RAII


Non-issue. You can use fopen in C++ and remember to fclose, too.


No, every time you have something that sound like "you just have to [...]" it means future bugs that were entirely preventable. The only correct way in c++ is to wrap it in a unique_ptr or handle type so that fclose gets called automatically when you are done with the resource


Use static analysers, just like you have to do on C and C++ to handle many of their flaws.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: