<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Netvouz / MondoTofu / tag / handling</title>
<link>http://netvouz.com/MondoTofu/tag/handling?feed=rss</link>
<description>MondoTofu&#39;s bookmarks tagged &quot;handling&quot; on Netvouz</description>
<item><title>Error hiding - Wikipedia, the free encyclopedia</title>
<link>https://en.wikipedia.org/wiki/Error_hiding</link>
<description>Error hiding is an anti-pattern in computer programming. The programmer hides error messages by overriding them with exception handling. As a result of this the root error message is hidden from the user (hence &#39;error hiding&#39;) and so they will not be told what the actual error is. Error hiding is a bane of support engineers&#39; jobs as it often delays the resolution of the problem by hiding information needed to identify what is going wrong.</description>
<category domain="http://netvouz.com/MondoTofu?category=6277193935135188477">Software Engineering</category>
<author>MondoTofu</author>
<pubDate>Thu, 19 May 2016 01:48:14 GMT</pubDate>
</item><item><title>System call error handling</title>
<link>http://uw714doc.sco.com/en/SDK_sysprog/SCL_SysCallErrHdl.html</link>
<description>System call error handling System calls that fail to complete successfully almost always return a value of -1 to your program. (If you look through the system calls in Section 2, you will see that there are a few calls for which no return value is defined, but they are the exceptions.) In addition to the -1 returned to the program, the unsuccessful system call places an integer in an externally declared variable, errno. In a C program, you can determine the value in errno if your program contains the following statement: #include &lt;errno.h&gt;</description>
<category domain="http://netvouz.com/MondoTofu?category=4997847696138980642">Unix Tips</category>
<author>MondoTofu</author>
<pubDate>Thu, 19 Jan 2012 22:19:47 GMT</pubDate>
</item></channel></rss>