{"id":640,"date":"2014-07-10T11:00:52","date_gmt":"2014-07-10T15:00:52","guid":{"rendered":"https:\/\/itp.nyu.edu\/physicalcomputing\/?page_id=640"},"modified":"2022-06-20T23:07:51","modified_gmt":"2022-06-21T03:07:51","slug":"variables","status":"publish","type":"page","link":"https:\/\/itp.nyu.edu\/physcomp\/lessons\/variables\/","title":{"rendered":"Variables"},"content":{"rendered":"\n

Adapted from Variables<\/a><\/em><\/p>\n\n\n\n

<\/span>Introduction<\/span><\/h2>\n\n\n\n

This tutorial explains how computer programs organize information in computer memory using variables. All computer programming languages use variables to manage memory, so it’s useful to understand this no matter what programming language or computer you’re using. Although the following was written with microcontrollers and physical computing applications in mind, it applies to programming in general.<\/p>\n\n\n\n

The programming language examples below use a syntax based on the programming language C. That same syntax is used by many other languages, including Arduino (which is written in C), Java, Processing (which is written in Java), JavaScript, and others.<\/p>\n\n\n\n

<\/span>What Is Computer Memory, Anyway?<\/span><\/h2>\n\n\n\n

A computer’s memory is basically a matrix of switches, laid out in a regular grid, not unlike the switches you see on the back of a lot of electronic gear as shown in Figure 1:<\/p>\n\n\n\n

\"Five
Figure 1. DIP Switches<\/figcaption><\/figure>\n\n\n\n

Each switch represents the smallest unit of memory, a bit.<\/strong>  If the switch is on, the bit’s value is 1. If it’s off, the value is 0. Each bit has an address in the grid. We can envision a grid that represents that memory like this:<\/p>\n\n\n\n

bit0<\/td>bit1<\/td>bit2<\/td>bit3<\/td>bit4<\/td>bit5<\/td>bit6<\/td>bit7<\/td><\/tr>
bit8<\/td>bit9<\/td>bit10<\/td>bit11<\/td>bit12<\/td>bit13<\/td>bit14<\/td>bit15<\/td><\/tr>
–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td><\/tr>
–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td><\/tr>
–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td><\/tr>
–<\/td>–<\/td>–<\/td>–<\/td>–<\/td><\/td>–<\/td>–<\/td><\/tr>
–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td><\/tr>
–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td><\/tr><\/tbody><\/table>
Table 1. All data that’s stored in computer memory is stored in these arrays of bits.<\/figcaption><\/figure>\n\n\n\n

<\/p>\n\n\n\n

So if a bit can be only 0 or 1, how do we get values greater than 1?<\/strong><\/p>\n\n\n\n

When you count normally, you count in groups of ten. This is because you have ten fingers. So to represent two groups of ten, you write “20”, meaning “2 tens and 0 ones”. This counting system is called base ten,<\/strong> or decimal notation<\/strong>. Each digit place in base ten represents a power of ten: 100 is 102<\/sup>, 1000 is 103<\/sup>, etc.<\/p>\n\n\n\n

Now, imagine you had only two fingers. You might count in groups of two. This is called base two<\/strong>, or binary notation<\/strong>.<\/em> So two, for which you write “2” in base ten, would be “10” in base two, meaning one group of two and 0 ones. Each digit place in base two represents a power of two: 100 is 22<\/sup>, or 4 in base ten, 1000 is 23<\/sup>, or 8 in base ten, and so forth.<\/p>\n\n\n\n

Any number you represent in decimal notation can be converted into binary notation by simply regrouping it in groups of two. Once you’ve got the number in binary form, you can store it in computer memory, letting each binary digit fill a bit of memory.  So the number 238 in decimal notation would be 11101110 in binary notation. The bits in memory used to store 238 would look like this:<\/p>\n\n\n\n

27<\/sup> (128)<\/td>26<\/sup> (64)<\/td>25<\/sup> (32)<\/td>24<\/sup> (16)<\/td>23<\/sup> (8)<\/td>22<\/sup> (4)<\/td>21<\/sup> (2)<\/td>20<\/sup> (1)<\/td><\/tr>
1<\/td>1<\/td>1<\/td>0<\/td>1<\/td>1<\/td>1<\/td>0<\/td><\/tr><\/tbody><\/table>
Table 2. The bits of the decimal value 238. 238 = 27<\/sup> (128) + 26 (64) +25<\/sup> (32) +23<\/sup> (8) + 22<\/sup> (4) + 21<\/sup> (2)<\/figcaption><\/figure>\n\n\n\n

<\/span>Arranging Memory into Variable Space<\/span><\/h3>\n\n\n\n

Programming languages organize computer memory by breaking the grid of bits up into smaller chunks and labeling them with names.  Those names are called variables, and they refer to a location in the computer’s memory. When you ask for the value of a variable, you’re asking what the states of the switches in that location in memory are.<\/p>\n\n\n\n

If you think of your program as a set of instructions, then variables are the words that you use to describe what those instructions act upon.<\/p>\n\n\n\n

For example:<\/p>\n\n\n\n

” When the user has pushed the button two times… “<\/p>\n\n\n\n

For this you need a variable called buttonPushed, and you need to check when it’s equal to 2:<\/p>\n\n\n

\nif (buttonPushed == 2)\n<\/pre><\/div>\n\n\n
When you want to store a piece of something like the number of times a button’s been pushed in the computer’s memory, you give it a name and a data type,<\/strong> which  states how much memory you intend to use. You usually give it an initial value as well. This is called declaring the variable<\/strong>, and it looks like this:<\/p>\n\n\n
\nint sensorValue = 234;\nbyte buttonPushed = 15;\nlong timeSinceStart = 10324;\nboolean isOpen = false;\n<\/pre><\/div>\n\n\n
<\/span>Data Types<\/span><\/h2>\n\n\n\n
Every variable has a data type<\/strong>. The data type of a variable determines how much of the computer’s memory the variable will occupy.  Different programming languages have different data types. The examples above use data types from the C programming language that Arduino uses.<\/p>\n\n\n\n
The first one, int sensorValue<\/tt>, is an integer data type. Ints in C take up 16 bits (32 bits in the 32-bit boards like the Nano 33 IoT), so they can contain 216<\/sup> different values (or 232<\/sup><\/sub>). Ints can only contain integers, but they can be positive or negative, so the variable sensorValue above could range from -32,768 to 32,767. That’s a range from -215<\/sup> to 215<\/sup>, with one bit used to store the plus or minus sign.<\/p>\n\n\n\n
The second, buttonPushed<\/tt>, is a byte<\/tt> data type. Bytes take up 8 bits, and can therefore store 28<\/sup> or 256 different values, from 0 to 255. Bytes in Arduino are unsigned<\/strong>, meaning that they can only be positive numbers.<\/p>\n\n\n\n
The third, timeSinceStart<\/tt> is a long int<\/tt>eger type, for storing very large values. In this instance, it might be storing the number of milliseconds since your program started, which can get big very quickly. Long ints are signed, and can range from -2,147,483,648 to 2,147,483,647. That’s 232<\/sup> possible values.<\/p>\n\n\n\n
The fourth, isOpen<\/tt>, is a boolean variable.  Booleans can only true or false, and ideally take up just one bit in memory (though most programming languages use a whole byte for convenience).<\/p>\n\n\n\n
0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td><\/tr>
1<\/td>1<\/td>1<\/td>0<\/td>1<\/td>0<\/td>1<\/td>0<\/td><\/tr>
0<\/td>0<\/td>0<\/td>0<\/td>1<\/td>1<\/td>1<\/td>1<\/td><\/tr>
0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td><\/tr>
0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td>0<\/td><\/tr>
0<\/td>0<\/td>1<\/td>0<\/td>1<\/td>0<\/td>0<\/td>0<\/td><\/tr>
0<\/td>1<\/td>0<\/td>1<\/td>0<\/td>1<\/td>0<\/td>0<\/td><\/tr>
0<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td>–<\/td><\/tr><\/tbody><\/table>
Table 3. A number of variables stored in a processor’s memory as 1s and 0s.<\/figcaption><\/figure>\n\n\n\n
<\/p>\n\n\n\n
When you declare a variable, the microcontroller picks the next available address and sets aside as many bits are needed for the data type you declare. If you declare a byte, for example, it sets aside 8 bits. An integer gets 16 bits. A string gets one byte (eight bits) for every character of the string, and a byte to end the string.<\/p>\n\n\n\n
<\/span>What About Fractional Numbers?<\/span><\/h3>\n\n\n\n
The variable types above are all for whole numbers, or integers. But how do you store a number like 3.1415 or 2.7828 or other fractional numbers?  These are called floating-point numbers<\/strong> in the programming world, and they’re a special type of variable called a float<\/strong>.  In Arduino, floats are actually 32-bit numbers, stored in 4 bytes of memory. A few of those bits are used to store the decimal point position.<\/p>\n\n\n\n
Depending on the processor you are using, the data types might be different sizes. Table 4 shows the different sizes for the data types on the Uno, an 8-bit processor, and the Nano 22 IoT, a 32-bit processor.<\/p>\n\n\n\n
Data Type<\/th>Uno<\/th>Nano 33 IoT<\/th><\/tr><\/thead>
byte<\/td>1 byte<\/td>1 byte<\/td><\/tr>
int<\/td>2 bytes<\/td>4 bytes<\/td><\/tr>
float<\/td>4 bytes<\/td>4 bytes<\/td><\/tr>
char<\/td>1 byte<\/td>1 byte<\/td><\/tr>
long<\/td>4 bytes<\/td>4 bytes<\/td><\/tr>
short<\/td>2 bytes<\/td>2 bytes<\/td><\/tr>
double<\/td>4 bytes<\/td>8 bytes<\/td><\/tr>
bool<\/td>1 byte<\/td>1 byte<\/td><\/tr><\/tbody><\/table>
Table 4. The basic Arduino data types and their relative sizes on the Uno and Nano 33 IoT<\/figcaption><\/figure>\n\n\n\n
<\/p>\n\n\n\n
Here’s a snippet of code to find out a given data type’s size on an Arduino:<\/p>\n\n\n
\nSerial.print(sizeof(int));\n<\/pre><\/div>\n\n\n
Replace int above with byte, bool, double, float, long, or the data type whose size you want to know. <\/p>\n\n\n\n
<\/span>Choosing the Right Data Type<\/span><\/h3>\n\n\n\n
How do you know what data type to choose when declaring variables? It depends on two factors: what you’re going to use the variables for, and what functions you plan to use on them. First, consider how likely the numbers you might store are likely to be. For example, if you’re counting button pushes, you’re unlikely to get more than a few hundred in a few minutes, so an int or a byte might be fine. But for a number that might get large, like counting the number of milliseconds since some past event, the number could get very large, so you might need a long int.<\/p>\n\n\n\n
Different built-in functions of a programming language will require different data types as parameters, so when you can, use data types that match the functions you plan to use.  For example, if you were using a variable to store the results of Arduino’s millis()<\/a><\/tt> function, you should use a long int, because millis()<\/tt> returns that data type.<\/p>\n\n\n\n
<\/span>Doing Math With Variables<\/strong><\/span><\/h2>\n\n\n\n
When you add, subtract, multiply, or divide with variables in a computer program, the results you get depend on the variable types you used. For example,  if you ran the function below:<\/p>\n\n\n
\nint voltage = 5;\nint divider = 2;\nint newVoltage = voltage \/ divider;\n<\/pre><\/div>\n\n\n
You might think that newVoltage = 2.5, right? Wrong. Because you used ints, the fractional part is gone, so the result would be 2.  Here’s another:<\/p>\n\n\n
\nbyte buttonPushes = 254;\nbuttonPushes = buttonPushes + 4;\n<\/pre><\/div>\n\n\n
After this, you’d expect that buttonPushes = 258, right? Wrong again!  Because you used a byte, you can’t store a value larger than 255, so when the result is larger than that, the number rolls over to the lowest possible value again. The result would be 2.<\/p>\n\n\n\n
Wait, what?<\/p>\n\n\n\n
Look at it this way. The highest value you can store in a byte is 255. Therefore, if you try to store 256, it rolls over to 0. 257 rolls over to 1. And 258 rolls over to 2. So 254 + 4 in a byte variable yields 2.  If you used an int instead of a byte, then you’d get the result you expect (258) because an int can hold values larger than 255.<\/p>\n\n\n\n
<\/span>Numeric Notation Systems<\/span><\/h2>\n\n\n\n
There are three notation systems used most commonly in programming languages to represent numbers: binary<\/strong> (base two), decimal<\/strong> (base ten), and hexadecimal<\/strong> (base sixteen). In hexadecimal notation, the letters A through F represent the decimal numbers 10 through 15. Furthermore, there is a system of notation called ASCII, which stands for American Standard Code for Information Interchange, which represents most alphanumeric characters from the romanized alphabet as number values. More on ASCII can be found in the pages on serial communication.<\/a> For more, see this online table<\/a> representing the decimal numbers 0 to 255 in decimal, binary, hexadecimal, and ASCII. While you can work mostly in decimal notation, there are times when it’s more convenient to represent numbers in ms other than base 10.<\/p>\n\n\n\n
Table 5 shows a few number values in the different bases, and the different notation forms:<\/p>\n\n\n\n
Decimal value<\/strong><\/td>Hexadecimal<\/strong><\/td>Binary<\/strong><\/td><\/tr>
 3<\/td>0x03<\/span><\/span><\/td>0b11<\/code><\/td><\/tr>
12<\/td>0x0C<\/span><\/span><\/td>0b1100<\/code><\/td><\/tr>
45<\/td>0x2D<\/code><\/td>0b101101<\/code><\/td><\/tr>
234<\/td>0xEA<\/code><\/td>0b11101010<\/code><\/td><\/tr>
1000<\/td>0x3E8<\/code><\/td>0b1111101000<\/code><\/td><\/tr><\/tbody><\/table>
Table 5. A few number values in base 10, and their equivalent values in binary (base 2)<\/figcaption><\/figure>\n\n\n\n
<\/p>\n\n\n\n
Because the values are all bits in the computer’s memory,  you can use all of these notation systems interchangeably. Here are a few examples:<\/p>\n\n\n
\nif (colorValue == 0xFF); \/\/ check to see if the color value is 255\n\n\/\/ add 5 to 0x90. Result will be 0x95:\nint channelNumber = 5;\nint midiCommand = 0x90 + channelNumber;\n<\/pre><\/div>\n\n\n
<\/span>Variable scope<\/strong><\/span><\/h2>\n\n\n\n
Variables are local<\/strong> to a particular function in your code if they are declared in that function. Local variables can’t be used by functions outside the one that declares them, and the memory space allotted to them is released  when the function ends. Variables are global<\/strong> when they are declared at the beginning of a program, outside all functions. Global variables are accessible to all functions in a the program, and their value is maintained for the duration of the program. Usually you use global variables for values that will need to be kept in memory for future use by other functions, and local variables when you know the value won’t be used outside that function. In general, it’s better to default to local variables when you can, to manage memory more efficiently. Here’s a typical example:<\/p>\n\n\n
\nint oldButtonPush = 0;  \/\/ global variable\n\nvoid setup() {\n   Serial.begin(9600);\n}\n\nvoid loop() {\n   int buttonPush = digitalRead(3); \/\/ local variable\n   if (buttonPush != lastButtonPush) {\n      \/\/ the button changed. Do something here\n      \/\/ then store the current button push state\n      \/\/ in the global variable for the next time\n      \/\/ through the loop:\n   oldButtonPush = buttonPush;  \n   }\n}\n<\/pre><\/div>\n\n\n
In this example, the variable buttonPush<\/tt> is local to the loop function. You couldn’t read it in the setup, or any other function. The variable oldButtonPush<\/tt>, on the other hand, is global, and can be read by any function. In the example above, the local variable is used to read the latest state of a digital input, and then later, the value is put into the global variable so that you can get a new reading and compare it to the old one.<\/p>\n\n\n\n
<\/span>Constants<\/span><\/h2>\n\n\n\n
In addition to variables, every programming language also includes constants<\/strong>, which are simply variables that don\u2019t change. They\u2019re a useful way to label and change numbers that get used repeatedly within your program. For example, imagine you’re writing a program that runs a servo motor. Servo motors have a minimum and maximum pulse width that doesn\u2019t change, although each servo\u2019s minimum and maximum might be somewhat different. Rather than change every occurrence of the minimum and maximum numbers in the program, we make them constants, so we only have to change the number in one place.<\/p>\n\n\n\n
You don\u2019t have to use constants in your programs, but they\u2019re handy to know about, and you will encounter them in other people\u2019s programs.<\/p>\n\n\n\n
In C and therefore in Arduino, there are two ways you can declare constants. You can use the const keyword, like so:<\/p>\n\n\n
\nconst int LEDpin = 3;\nconst int sensorMax = 253;\n<\/pre><\/div>\n\n\n
Or you can use  define<\/strong>:<\/p>\n\n\n
\n#define LEDPin 3\n#define sensorMax 253\n<\/pre><\/div>\n\n\n
Defines are always preceded by a #, and are don’t have a semicolon at the end of the line. Defines always come at the beginning of the program. They actually work a bit like aliases. What happens is that you define a number as a name, and before compiling, the compiler checks for all occurrences of that name in the program and replaces it with the number. This way, defines don’t take up any memory, but you get all the convenience of a named constant. There are several defines in the libraries of the Arduino core libraries, so it’s preferable to use const instead of #define for constants.<\/p>\n\n\n\n
For more on variables in Arduino, see the variable reference page<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Adapted from Variables Introduction This tutorial explains how computer programs organize information in computer memory using variables. All computer programming languages use variables to manage memory, so it’s useful to understand this no matter what programming language or computer you’re using. Although the following was written with microcontrollers and physical computing applications in mind, it applies … Continue reading “Variables”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":13,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"categories":[11,52,26],"tags":[],"class_list":["post-640","page","type-page","status-publish","hentry","category-code","category-lesson","category-programming"],"_links":{"self":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/640"}],"collection":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/comments?post=640"}],"version-history":[{"count":28,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/640\/revisions"}],"predecessor-version":[{"id":9790,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/640\/revisions\/9790"}],"up":[{"embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/pages\/13"}],"wp:attachment":[{"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/media?parent=640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/categories?post=640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itp.nyu.edu\/physcomp\/wp-json\/wp\/v2\/tags?post=640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}