#6 Check return codes everywhere

[Markus Elfring]

Some checks for return codes are missing.

Examples:
Would you like to add more error handling for return values from "fprintf" in functions like "on_connection_information_changed" and "create_pixbuf"?
http://avpgcon.svn.sourceforge.net/viewvc/avpgcon/trunk/gavpgcon/src/callbacks.c?revision=44&view=markup
http://avpgcon.svn.sourceforge.net/viewvc/avpgcon/trunk/gavpgcon/src/support.c?revision=19&view=markup

[Steffen Macke]

Logged In: YES
user_id=30248
Originator: NO

Thanks for the hint. I don't think I'll be able to work on this issue
during the next month. For the time being, patches are welcome.

[Markus Elfring]

How do you think about to look for any remaining issues by static source
code analysis?
http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#C

How do you think about to identify update candidates by compiler-specific
extensions like the annotation "__attribute__
((__warn_unused_result__))"?
http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Function-Attributes.html

Which reaction do you like more for failed function calls?
http://en.wikipedia.org/wiki/Crash-only_software

Would you like to reduce the efforts for error code checking by an exception class hierarchy?
http://dietmar-kuehl.de/mirror/c++-faq/exceptions.html#faq-17.1
http://cexcept.sourceforge.net/