https://bugs.kde.org/show_bug.cgi?id=400632

--- Comment #8 from Markus Elfring <markus.elfr...@web.de> ---
(In reply to Christoph Cullmann from comment #7)
> 1) we can't do anything then anyways, …
Can you catch a C++ exception in the function “main” and choose a more
appropriate program error code?


> 2) you will get that close to never, as e.g. Linux over-commits,
System administrators can select other settings.
https://lwn.net/Articles/317814/


>    you will just later silently segfault
>    (and yes, that is the cruel reality, in my daily work I must always cope
>    with that)
Did you get used also to any special software situations?


> No, but you can provide patches for improvements, but please not for
> exceptions safety issues
Would you pick any change possibilities up for better software maintenance?


> that just not exist given the lack of them.
Exception-unsafety exists if a compilation parameter like “-fno-exceptions”
will be omitted from a software build configuration, won't it?


> If you can point out that we have a leak, crash, ...,
> please open a bug for that.
I have tried this here once again.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to