<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Framebuffer on Siddharth Mishra</title><link>http://brightprogrammer.in/tags/framebuffer/</link><description>Recent content in Framebuffer on Siddharth Mishra</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 13 Jun 2026 09:04:24 -0700</lastBuildDate><atom:link href="http://brightprogrammer.in/tags/framebuffer/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating Our Own 'puts'</title><link>http://brightprogrammer.in/posts/creating-our-own-puts/</link><pubDate>Sun, 09 Jan 2022 00:00:00 +0000</pubDate><guid>http://brightprogrammer.in/posts/creating-our-own-puts/</guid><description>&lt;p>Well, the title can be misleading. We will be eventually implementing our own &amp;lsquo;puts&amp;rsquo; function but for now it&amp;rsquo;s not named puts. The function will be analogous to puts. This function will actually be to help us debug things. After this chapter we will be adding more and more features to our OS and we need a method to see if it worked or not. This method can be anything! For eg : changing the screen colour to red (for error) or blue (for success). We print an error message if something bad happens.&lt;/p></description></item></channel></rss>