{"id":467,"date":"2014-02-15T00:01:58","date_gmt":"2014-02-15T08:01:58","guid":{"rendered":"http:\/\/c-for-dummies.com\/blog\/?p=467"},"modified":"2014-05-06T08:09:11","modified_gmt":"2014-05-06T15:09:11","slug":"the-ongoing-mystery-of-the-variable","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=467","title":{"rendered":"The Ongoing Mystery of the ** Variable"},"content":{"rendered":"

The **<\/code> notation can really make a beginning C programmer blanch. In fact, a lot of Java programmers probably fled from the C language just after the initial lesson on pointers. They’d turn to stone even to glance at a variable like **blorf<\/code>. You don’t need to cower under a desk with those people.
\n
\nSuppose an int<\/em> pointer is declared as ptr<\/code>:<\/p>\n

int *ptr;<\/code><\/p>\n

To use the pointer you have to initialize it, storing the address of some other int<\/em> variable in the pointer, because:<\/p>\n

A pointer is a variable that holds a memory location. Specifically it holds the address of another variable.<\/p><\/blockquote>\n

For example, variable i<\/code>:<\/p>\n

ptr = &i;<\/code><\/p>\n

After that declaration in the code, pointer variable ptr<\/code> holds the address of variable i<\/code>. This process should be familiar to you if you read through one of my C programming books. Here’s some code you can chew on for review:<\/p>\n

\r\n#include <stdio.h>\r\n\r\nint main()\r\n{\r\n    int i;\r\n    int *ptr;\r\n\r\n    i = 4;      \/* initialize i *\/\r\n    ptr = &i;   \/* initialize ptr *\/\r\n\r\n    printf(\"i is %d\\n\",i);\r\n    printf(\"&i is %p\\n\",&i);\r\n    printf(\"*ptr is %d\\n\",*ptr);\r\n    printf(\"ptr is %p\\n\",ptr);\r\n\r\n    return(0);\r\n}<\/pre>\n
The code shows how the pointer and variable are related. Here’s sample output:<\/p>\n
i is 4\r\n&i is 0028FF18\r\n*ptr is 4\r\nptr is 0028FF18<\/code><\/pre>\n
Figure 1 shows the Watches window in Code::Blocks, which further demonstrates the equivalency between the variables. Pay attention to the far right column, which lists the variable types. See how both &i<\/code> and ptr<\/code> are basically the same type, int *<\/code>, which means an integer pointer, or the memory location of an integer value.<\/p>\n
\"Figure
Figure 1. The Watches window shows how the variable values and types are equivalent.<\/p><\/div>\n
Just for giggles, Figure 2 illustrates the bytes stored at memory location 0x28ff18<\/code>. Integer values on my PC are stored in 32 bits, which is 4 bytes wide. You can see the value 4 stored in those four bytes, highlighted in the figure. (The value is stored backwards in memory, which is good for the processor, but not for humans reading a data dump.)<\/p>\n
\"Figure
Figure 2. The value of variable i<\/code> as stored in memory.<\/p><\/div>\n
As with all variables, a pointer variable has a location in memory. To obtain that location, the unary &<\/code> operator is used. The end result, the address of a pointer variable, is effectively a pointer-to-a-pointer.<\/p>\n
Don’t let that sink in; just keep reading!<\/em><\/p>\n
The address of a pointer variable is where those weird **<\/code> things come from. That’s because a variable with two unary *<\/code> operators is a pointer-to-a-pointer.<\/p>\n
Consider the following code, which adds a pointer-to-a-pointer variable, ptr2ptr<\/code>, to the original code listed earlier:<\/p>\n
\r\n#include <stdio.h>\r\n\r\nint main()\r\n{\r\n    int i;\r\n    int *ptr;\r\n    int **ptr2ptr;\r\n\r\n    i = 4;\r\n    ptr = &i;\r\n                \/* initialize ptr2ptr: *\/\r\n    ptr2ptr = &ptr;\r\n\r\n    printf(\"i is %d\\n\",i);\r\n    printf(\"&i is %p\\n\",&i);\r\n    printf(\"*ptr is %d\\n\",*ptr);\r\n    printf(\"ptr is %p\\n\",ptr);\r\n                \/* new stuff here: *\/\r\n    putchar('\\n');\r\n    printf(\"&ptr is %p\\n\",&ptr);\r\n    printf(\"ptr2ptr is %p\\n\",ptr2ptr);\r\n    printf(\"*ptr2ptr is %p\\n\",*ptr2ptr);\r\n\r\n    return(0);\r\n}<\/pre>\n
The ptr2ptr<\/code> variable is initialized at Line 12. It’s assigned the address of the ptr<\/code> pointer. A **<\/code> variable like ptr2ptr<\/code> holds the address of a pointer. In this code that pointer is an int<\/em> pointer, *ptr<\/code>.<\/p>\n
Here’s the program output, along with my comments (in red) explaining the last three lines:<\/p>\n
i is 4\r\n&i is 0028FF18\r\n*ptr is 4\r\nptr is 0028FF18\r\n\r\n&ptr is 0028FF14      The address of variable ptr in memory<\/span>\r\nptr2ptr is 0028FF14   Also the address of variable ptr in memory<\/span>\r\n*ptr2ptr is 0028FF18  The address of variable i in memory<\/span><\/code><\/pre>\n
The memory address of ptr<\/code> is fetched by using the &<\/code> operator. In the above output, that location is 0x28FF14<\/code>.<\/p>\n
Variable ptr2ptr<\/code> stores the address of variable ptr<\/code>. You can see that by the second to last line of output. Both lines display 0x28FF14<\/code>.<\/p>\n
At the last line, the contents of variable ptr2ptr<\/code> when used with the unary *<\/code> operator are the same as the contents of the ptr<\/code> variable, the address of variable i<\/code>.<\/p>\n
The final step is to add the following line to the code, just after the last printf()<\/em> statement above the return<\/em> statement:<\/p>\n
printf(\"**ptr2ptr is %d\\n\",**ptr2ptr);<\/code><\/pre>\n
Compile and run on your own. Doing so will help you better understand what’s going on, or at least take you one step closer. I’ll explain more in next week’s Lesson<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
I continue my exploration of pointers-to-pointers by attempting to clear up how a **ptr<\/em> thing can be used in your code. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-467","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/467","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=467"}],"version-history":[{"count":11,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/467\/revisions"}],"predecessor-version":[{"id":715,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/467\/revisions\/715"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=467"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=467"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=467"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}