<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Error-Handling on Siddharth Mishra</title><link>http://brightprogrammer.in/tags/error-handling/</link><description>Recent content in Error-Handling on Siddharth Mishra</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 14 Jun 2026 21:53:10 -0700</lastBuildDate><atom:link href="http://brightprogrammer.in/tags/error-handling/index.xml" rel="self" type="application/rss+xml"/><item><title>How I Do Error Handling in C</title><link>http://brightprogrammer.in/posts/error-handling-in-c/</link><pubDate>Fri, 13 Dec 2024 00:00:00 +0000</pubDate><guid>http://brightprogrammer.in/posts/error-handling-in-c/</guid><description>&lt;p>This is not actually supposed to be a post because I think everyone has their own way of doing
things. This post I&amp;rsquo;m writing is just to overcome the FOMO of not writing enough blog posts, but
owning a domain and constantly keeping up my Pi4 to host this static website. Also because good
software engineers recommend making a habit of writing a blog post regularly.&lt;/p>
&lt;h1 id="the-problem">The Problem&lt;/h1>
&lt;p>You&amp;rsquo;re writing lots of functions in your program and it&amp;rsquo;s possible for those functions to fail
and you want to know when they fail. Say you&amp;rsquo;re creating a &lt;code>Vector&lt;/code> implementation in C and
you want to know whether the &lt;code>VectorPushBack&lt;/code> method you wrote will fail or succeed in inserting
element.&lt;/p></description></item></channel></rss>