https://bugs.kde.org/show_bug.cgi?id=400632
--- Comment #2 from Markus Elfring <markus.elfr...@web.de> --- (In reply to Dominik Haumann from comment #1) > In the Qt and KDE world exceptions are pretty much not used at all. They can eventually be thrown because of standard functionality by the C++ programming language. > So if an exception is thrown and no one catches it, > the application will crash just like before. Would you like to achieve an adjusted software behaviour for a robust text editor? > Besides that, it is also common in Qt to have the parent/child hierarchy, > so many objects' lifetime is managed by the parent QObject; Does this information apply to the mentioned source code places (which I pointed out as update candidates)? > in this case we do not need a unique_ptr at all typically. This can be fine for other software situations. > Since there is no particular issue here at hand that needs a fix, Do you care for advice from known programming guide lines? https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#r11-avoid-calling-new-and-delete-explicitly > I'll close as "not a bug" for now. I suggest to reconsider this view. Does this software still depend on a build configuration which uses a compilation parameter like “-fno-exceptions”? -- You are receiving this mail because: You are watching all bug changes.
