<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>flags on Bald Engineer</title><link>https://www.baldengineer.com/tag/flags</link><description>Recent content in flags on Bald Engineer</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 15 Jul 2015 18:47:57 +0000</lastBuildDate><atom:link href="https://www.baldengineer.com/tag/flags/index.xml" rel="self" type="application/rss+xml"/><item><title>Flag variables are not evil (for Microcontrollers)</title><link>https://www.baldengineer.com/flag-variables-are-not-evil-for-microcontrollers.html</link><pubDate>Wed, 15 Jul 2015 13:00:13 +0000</pubDate><guid isPermaLink="false">https://www.baldengineer.com/?p=5206</guid><description>Getting programming questions answered on the internet can be problematic. Programmers love to have opinions, stick to those ideas, and express them to you even when their opinion has nothing to do with your question(s).&#10;Not only am I going to explain how to use flag variables in your code, I am going to encourage their use—which most programmers avoid.&#10;However, this advice comes with two caveats.&#10;This information only applies to limited resource environments like an Arduino, LaunchPad or PIC. Use flag variables very carefully when you do use them. The following flag variable usage examples are Arduino-centric but apply to any microcontroller platform, including the Energia project for TI Launchpads.&gt; Flag variables are a Good Thing(tm) – when used properly<p><img src="https://www.baldengineer.com/wp-content/uploads/2015/07/fun-with-flag-variables.png" alt="Flag variables are not evil (for Microcontrollers)"/></p></description></item></channel></rss>