Markus Elfring

:crystal_ball: I am curious how such an issue will evolve further.

The mentioned function replacement could work. Would you like to consider other software design options? - [sigwaitinfo()](http://pubs.opengroup.org/onlinepubs/9699919799/functions/sigwaitinfo.html) - [Self-pipe trick](http://cr.yp.to/docs/selfpipe.html) - [Signal-safe locks](http://locklessinc.com/articles/signalsafe_locks/)

I suggest to reconsider specific source code places.

Do you see any more update candidates for this issue?

How do you think about a software design which would work with plug-ins (or add-ons)?

I suggest to avoid [ignorance of return values](https://cwe.mitre.org/data/definitions/252.html "Checking more return values") a bit more. Would you like to detect every error situation as early as possible?

* How do you think about to improve [static source code analysis](https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#C.2C_C.2B.2B "Tools for code analysis") also for this software? * Would you like to choose [a more appropriate program...

* Are you interested to apply [aspect-oriented software development](http://aspectc.org/ "Software development with AspectC++?")? * How do you think about to encapsulate error detection and corresponding exception handling as [a reusable...

:thought_balloon: Would you become interested to [use a development tool like “clang-tidy” for corresponding source code adjustments](https://clang.llvm.org/extra/clang-tidy/checks/readability-delete-null-pointer.html "Deletion of unnecessary null pointer checks")? ----- How do you think about to...

How do you think about to improve the software situation any more by influencing evolution according to development tools for automatic source code adjustments? :thinking: