[gpm] Check return codes everywhere

[Markus Elfring]

> There are more than just some :-)
>   

Thanks for your acknowledgement.


> But yes, in general everything that could result in an error
> should be caught.
>   

How do you think about the reaction "exit(errno)" or "abort()"?

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/

Are there any chances to apply usual advices by tools from the software
area "aspect-oriented programming"?
http://research.msrg.utoronto.ca/ACC/Tutorial#A_Reusable_Aspect_for_Memory_All

Regards,
Markus