{"id":5783,"date":"2023-03-08T00:01:10","date_gmt":"2023-03-08T08:01:10","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=5783"},"modified":"2023-03-04T09:22:09","modified_gmt":"2023-03-04T17:22:09","slug":"merging-arrays-solution","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=5783","title":{"rendered":"Merging Arrays – Solution"},"content":{"rendered":"

This month’s Exercise<\/a> is about coding a merge()<\/em> function, which swallows two arrays and generates a third as output. The new array is “zippered” from the original arrays, alternating values from each.
\n
\nMy merge()<\/em> function solution involves two steps.<\/p>\n

First, allocate storage for the new array. Because both arrays are the same size; only one size value is passed as an argument:<\/p>\n

int *merge(int *a, int *b, int s)<\/code><\/p>\n

If the two arrays were different sizes, two size arguments are required, each paired with its array. Either way, storage is allocated for the new array, which is assumed to be an integer data type.<\/p>\n

Second, loop through the two arrays, packing the newly-allocated array with alternating values from each of the two passed arrays. Two variables help move through the arrays: offset<\/code> for the new array and index<\/code> for the two passed arrays. Here is my merge()<\/em> function:<\/p>\n

\r\nint *merge(int *a, int *b, int s)\r\n{\r\n    int *r,offset,index;\r\n\r\n    \/* allocate maximum stroage *\/<\/span>\r\n    r = malloc( sizeof(int) * s * 2 );\r\n\r\n    if( r!=NULL )\r\n    {\r\n        offset = index = 0;\r\n        while( offset<s*2 )\r\n        {\r\n            r[offset++] = *(a+index);\r\n            r[offset++] = *(b+index);\r\n            index++;\r\n        }\r\n    }\r\n    return(r);\r\n}<\/pre>\n
The function returns the address of int<\/em> pointer r<\/code>, which is allocated as the first step. Providing the result isn’t NULL<\/code>, values from each of the passed arrays, a<\/code> and b<\/code>, are assigned to sequential offsets in the new array.<\/p>\n
Variable offset<\/code> is incremented after each value is added to array r<\/code>, but variable index<\/code> is incremented only after processing both arrays a<\/code> and b<\/code>.<\/p>\n
When the function is complete, address r<\/code> is returned, though in the main()<\/em> function I don’t test for NULL<\/code>. Instead, the following statements handle the function call and the output:<\/p>\n
\r\n    c = merge(a,b,SIZE);\r\n    printf(\"Merged: \");\r\n    for( x=0; x<SIZE*2; x++ )\r\n        printf(\" %2d\",c[x]);\r\n    putchar('\\n');\r\n<\/pre>\n
Though variable c<\/code> is declared as a pointer, and used in the merge()<\/em> function call that way, I use array notation when c<\/code>‘s values are output in the loop. This type of conversion is okay, and it keeps with the use of the other arrays in the main()<\/em> function.<\/p>\n
Click here<\/a> to view the full code on GitHub. I hope your solution worked out well and that the new array shows the proper data in sequence, zippered by the merge()<\/em> function.<\/p>\n","protected":false},"excerpt":{"rendered":"
This month’s Exercise is about coding a merge() function, which swallows two arrays and generates a third as output. The new array is “zippered” from the original arrays, alternating values from each.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-5783","post","type-post","status-publish","format-standard","hentry","category-solution"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/5783","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=5783"}],"version-history":[{"count":3,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/5783\/revisions"}],"predecessor-version":[{"id":5794,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/5783\/revisions\/5794"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}