<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>avr-gcc on Bald Engineer</title><link>https://www.baldengineer.com/tag/avr-gcc</link><description>Recent content in avr-gcc on Bald Engineer</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 24 Mar 2015 22:13:55 +0000</lastBuildDate><atom:link href="https://www.baldengineer.com/tag/avr-gcc/index.xml" rel="self" type="application/rss+xml"/><item><title>Const vs #define - When do you use them and why?</title><link>https://www.baldengineer.com/const-vs-define-when-do-you-them-and-why.html</link><pubDate>Thu, 14 Nov 2013 11:13:40 +0000</pubDate><guid isPermaLink="false">https://www.baldengineer.com/?p=1944</guid><description>&lt;p&gt;Arduino boards have microcontrollers with notoriously small amounts of RAM.  The Uno only has 2,048 bytes of static RAM available for your program to store variables.  So when you need to keep non-changing variables out of RAM which is best to use const or #define?&lt;/p&gt;&#10;&lt;h2 id="what-is-define"&gt;What is #define&lt;/h2&gt;&#10;&lt;p&gt;#define is often misunderstood because it isn&amp;rsquo;t a programming statement.  Instead, it sets up a macro which causes a text replace to occur before code is compiled.  For example in this code:&lt;/p&gt;</description></item></channel></rss>