Completion of error handling

[elfring]

Would you like to add more error handling for return values from functions like the following?

• realloc ⇒ main
• pthread_mutex_init ⇒ setup_server

[mom040267]

The errors, if happened in those places, are the sign that something is very very wrong with the system. Those errors may never happen under normal circumstances. If the server crashes after that, that's totally OK.

[elfring]

I suggest to avoid ignorance of return values a bit more.

Are you interested to apply aspect-oriented software development?
How do you think about to encapsulate error detection and corresponding exception handling as a reusable aspect in your software?

[mom040267]

no, I think that we are good with what we have now.

Thanks
Oleg

On Sat, Aug 29, 2015 at 12:52 AM, Markus Elfring notifications@github.com
wrote:

I suggest to avoid ignorance of return values
https://cwe.mitre.org/data/definitions/252.html a bit more.

Are you interested to apply aspect-oriented software development
http://aspectc.org/?
How do you think about to encapsulate error detection and corresponding
exception handling as a reusable aspect
http://en.wikipedia.org/wiki/Aspect_%28computer_programming%29 in your
software?

—
Reply to this email directly or view it on GitHub
#18 (comment).

[elfring]

Would you like to detect every error situation as early as possible?
How do you think about to improve static source code analysis also for your software?

Do you find information sources like the following useful?

• Article "A Reusable Aspect for Memory Allocation Checking"
• Document "Aspect-Oriented Software Development - An Introduction" by Johan Brichau and Theo D'Hondt
• Paper "On Typesafe Aspect Implementations in C++" by Daniel Lohmann and Olaf Spinczyk