{"id":7209,"date":"2025-10-25T00:01:21","date_gmt":"2025-10-25T07:01:21","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=7209"},"modified":"2025-10-18T11:13:22","modified_gmt":"2025-10-18T18:13:22","slug":"filling-the-pointer-pointers-with-data","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=7209","title":{"rendered":"Filling the Pointer Pointers with Data"},"content":{"rendered":"

The final step of the pointer storage program is to add data to the various buffers, or “sticks,” where ten integer values are stored. This step involves ugly double-pointer notation. If you can, please review last week’s Lesson<\/a> to get up to speed on how storage is allocated and how these pointers are managed.
\n
\nWhen I first coded this program, I wrote it in the manner presented over the past few weeks, one step at a time. I feel that the best way to write something weird like managing pointers is to do so incrementally. The final step is to add values to each of the allocated sticks and then output the values once everything is allocated.<\/p>\n

The following code adds two items to the code shown in last week’s Lesson: statements to assign the values and statements to output the results. Both use a similar oddball expression to access the individual values, which is the point of this Lesson.<\/p>\n

2025_10_25-Lesson.c<\/a><\/h3>\n
\r\n#include <stdio.h>\r\n#include <stdlib.h>\r\n#include <time.h>\r\n\r\n\/* allocate storage for ten integers *\/<\/span>\r\nint *ten(void)\r\n{\r\n    int *iptr = NULL;\r\n\r\n    iptr = malloc( sizeof(int) * 10 );\r\n\r\n    return(iptr);\r\n}\r\n\r\nint main()\r\n{\r\n    int **tenint = NULL;\r\n    int x,y;\r\n\r\n    \/* seed the randomizer *\/<\/span>\r\n    srand( (unsigned)time(NULL) );\r\n\r\n    \/* allocate 10 sticks of 10 integers *\/<\/span>\r\n    for( y=0; y<10; y++ )\r\n    {\r\n        \/* allocate first stick *\/<\/span>\r\n        if( tenint==NULL )\r\n        {\r\n            tenint = malloc( sizeof( int *) );\r\n            if( tenint==NULL )\r\n            {\r\n                fprintf(stderr,\"Unable to allocate storage\\n\");\r\n                exit(1);\r\n            }\r\n        }\r\n        else\r\n        \/* allocate additional sticks *\/<\/span>\r\n        {\r\n            tenint = realloc(tenint, sizeof( int *) * (y+1) );\r\n            if( tenint==NULL )\r\n            {\r\n                fprintf(stderr,\"Unable to reallocate storage\\n\");\r\n                exit(1);\r\n            }\r\n        }\r\n        \/* get the storage *\/<\/span>\r\n        *(tenint+y) = ten();\r\n        if( *(tenint+y)==NULL )\r\n        {\r\n            fprintf(stderr,\"Unable to allocate stick %d\\n\",y);\r\n            exit(1);\r\n        }\r\n        printf(\"Stick %d allocated\\n\",y);\r\n\r\n        \/* assign the values *\/<\/span>\r\n        for( x=0; x<10; x++ )\r\n            *(*(tenint+y)+x) = rand() % 10 + 10*(y+1);\r\n    }\r\n\r\n    \/* output the results *\/<\/span>\r\n    for( y=0; y<10; y++ )\r\n    {\r\n        printf(\"Stick %d: \",y);\r\n        for( x=0; x<10; x++ )\r\n            printf(\"%3d \",*(*(tenint+y)+x) );\r\n        putchar('\\n');\r\n    }\r\n\r\n    \/* clean-up *\/<\/span>\r\n    for( y=0; y<10; y++ )\r\n        free( *(tenint+y) );\r\n    free(tenint);\r\n    puts(\"All sticks freed\");\r\n    return 0;\r\n}<\/pre>\n
The first new bit of code appears inside the nested loop, under the comment \/* assign the values *\/<\/code>:<\/p>\n
for( x=0; x<10; x++ )
\n    *(*(tenint+y)+x) = rand() % 10 + 10*(y+1);<\/code><\/p>\n
The right side of the expression generates a random value based on the value of variable y<\/code>. The left side of the equation features this contraption:<\/p>\n
*(*(tenint+y)+x)<\/code><\/p>\n
As with anything ugly in programming, it helps to work from the inside out.<\/p>\n
tenint<\/code> is the address were a series of pointers are stored.<\/p>\n
tenint+y<\/code> is an offset into the buffer where the pointers are stored. It represents addresses (pointers) zero through y<\/code>, as stored in the tenint<\/code> buffer.<\/p>\n
*(tenint+y)<\/code> is the address stored at offset y<\/code>. So if y==3<\/code>, *(tenint+y)<\/code> represents the fourth value (address) stored in the buffer, the location of a ten-integer stick in memory. An equivalent in array notation would be tenint[y]<\/code>. (But remember that array notation isn’t a substitute for using pointers.)<\/p>\n
*(tenint+y)+x<\/code> is an offset from the address *(tenint+y)<\/code>. The result is still an address, but at an offset within the stick where the ten integers are stored. For example, if x==7<\/code>, *(tenint+y)+x<\/code> is the address of the eighth integer in the stick. The array notation equivalent would be tenint[y][x]<\/code>. This value is still an address.<\/p>\n
*(*(tenint+y)+x)<\/code> is a value, the integer, stored at address *(tenint+y)+x<\/code>.<\/p>\n
As the value of x<\/code> increases, each subsequent integer in the stick is fetched. Then the outer y<\/code> loop repeats to reference the next stick stored in the tenint<\/code> buffer.<\/p>\n
Here’s the program’s output:<\/p>\n
Stick 0 allocated
\nStick 1 allocated
\nStick 2 allocated
\nStick 3 allocated
\nStick 4 allocated
\nStick 5 allocated
\nStick 6 allocated
\nStick 7 allocated
\nStick 8 allocated
\nStick 9 allocated
\nStick 0:  14  19  10  15  18  14  15  17  16  14 
\nStick 1:  22  26  21  29  23  22  20  20  29  23 
\nStick 2:  38  36  33  30  36  32  32  37  37  34 
\nStick 3:  46  43  45  48  40  43  44  46  40  40 
\nStick 4:  52  54  58  55  56  52  58  56  54  59 
\nStick 5:  60  65  67  65  65  64  67  69  63  66 
\nStick 6:  75  71  71  70  79  71  75  75  77  75 
\nStick 7:  85  81  82  84  87  88  88  85  84  82 
\nStick 8:  96  94  99  93  99  95  97  98  96  91 
\nStick 9: 104 102 102 105 102 104 109 108 109 106 
\nAll sticks freed<\/code><\/p>\n
The point to all this is to manage a collection of allocated addresses, expanding this collection as new sticks are added. A more common way to deal with such an operation might be to create a linked list. But my point is more to teach the double-pointer concept when it comes to allocating, managing, and accessing storage.<\/p>\n","protected":false},"excerpt":{"rendered":"
Time to wrap up the code by putting data into the buffers, then accessing the data by using a double-pointer. 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-7209","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\/7209","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=7209"}],"version-history":[{"count":3,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/7209\/revisions"}],"predecessor-version":[{"id":7216,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/7209\/revisions\/7216"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7209"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7209"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7209"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}