{"id":5628,"date":"2022-11-19T00:01:35","date_gmt":"2022-11-19T08:01:35","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=5628"},"modified":"2022-11-26T09:02:44","modified_gmt":"2022-11-26T17:02:44","slug":"plotting-the-knights-next-move","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=5628","title":{"rendered":"Plotting the Knight’s Next Move"},"content":{"rendered":"

\"\"
\nThe next step in hopping a knight around a chessboard is determining which squares from its current position represent valid moves. Code must be combined from last week’s lesson<\/a> (setting the knight on the chessboard at a random spot) with the movement code presented a few lessons back.
\n
\nFigure 1 shows the results desired, with the knight’s random position marked by the letter K and valid potential moves shown as asterisks.<\/p>\n

\"knight

Figure 1. Potential moves for a knight on a chessboard.<\/p><\/div>\n

To plot the knight’s moves I created the moveto()<\/em> function. It accepts the knight’s current position (k<\/code>) and an array of potential moves (m[]<\/code>) as arguments. The knight’s position is randomly set in the main()<\/em> function. The array of potential moves is also declared there, but its values are initialized in the moveto()<\/em> function:<\/p>\n

\r\n\/* plot the knight moves\r\n   k = position\r\n   m[] = array to hold potential moves *\/<\/span>\r\nvoid moveto(int k, int m[])\r\n{\r\n    struct position {\r\n        int row;\r\n        int col;\r\n    };\r\n    \/* offsets to move the knight *\/<\/span>\r\n    struct position pairs[KM] = {\r\n        { -2,-1 }, { -2, 1 }, { -1, -2 }, { -1, 2 },\r\n        { 1, -2 }, { 1, 2 }, { 2, -1 }, { 2, 1 }\r\n    };\r\n    int x,krow,kcol,r,c;\r\n\r\n    \/* calculate knight's row and column\r\n       to make later calculations more\r\n       readable *\/<\/span>\r\n    kcol = k % SIZE;\r\n    krow = (k - kcol)\/SIZE;\r\n    \/* plot the potential knight moves\r\n       up to KM (8) of them *\/<\/span>\r\n    for( x=0; x<KM; x++ )\r\n    {\r\n        \/* find new square position *\/<\/span>\r\n        r = krow + pairs[x].row;\r\n        c = kcol + pairs[x].col;\r\n        \/* check for valid moves *\/<\/span>\r\n        if( (r<0 || r>=SIZE) || (c<0 || c>=SIZE) )\r\n        {\r\n            \/* square is out of bounds *\/<\/span>\r\n            m[x] = -1;\r\n        }\r\n        else\r\n        {\r\n            \/* plot position *\/<\/span>\r\n            m[x] = r * SIZE + c;\r\n        }\r\n    }\r\n}<\/pre>\n
The knight’s row (krow<\/code>) and column (kcol<\/code>) position is obtained from these expressions:<\/p>\n
kcol = k % SIZE;
\nkrow = (k - kcol)\/SIZE;<\/code><\/p>\n
This translation is necessary as the pairs[]<\/code> array uses row and column offsets.<\/p>\n
A for<\/em> loop processes all potential moves, zero through KM<\/code>. For each pairs[]<\/code> value, a row (r<\/code>) and column (c<\/code>) is obtained:<\/p>\n
r = krow + pairs[x].row;
\nc = kcol + pairs[x].col;<\/code><\/p>\n
An if<\/em> test confirms whether the row\/column value is in range:<\/p>\n
if( (r<0 || r>=SIZE) || (c<0 || c>=SIZE) )<\/code><\/p>\n
If the row (r<\/code>) or column (c<\/code>) is out of range, -1 is set in the m[]<\/code> array. Otherwise, the position is plotted and set in the array as a linear value:<\/p>\n
m[x] = r * SIZE + c;<\/code><\/p>\n
The array argument m[]<\/code> need not be returned from the moveto()<\/em> function. It’s one of those weird array\/pointer things that works in C.<\/p>\n
The main()<\/em> function is updated to add the moveto()<\/em> function call. Also the chess_board()<\/em> function is updated to accept the moves[]<\/code> array as a second argument. A for<\/em> loop is added to the function to process the moves[]<\/code> array, setting asterisks in those squares where the knight can move and ignoring the -1 values in the array.<\/p>\n
The full code is available on GitHub<\/a>. The output doesn’t yet match Figure 1 as the number of valid moves isn’t counted. Remember: One step at a time!<\/p>\n
Once I got the first version of the code to work, I added another function, movecount()<\/em>. This function processes the moves[]<\/code> array, determining how many moves are valid. It tallies those elements not equal to -1.<\/p>\n
\r\n\/* count the valid moves\r\n   m[] = array of move counts\r\n   -1 value for no move *\/<\/span>\r\nint movecount(int m[])\r\n{\r\n    int x,count;\r\n\r\n    count = 0;\r\n    \/* scan the array and tally values\r\n       zero or greater (non -1) *\/<\/span>\r\n    for( x=0; x<KM; x++ )\r\n    {\r\n        if( m[x] >= 0 )\r\n            count++;\r\n    }\r\n\r\n    return(count);\r\n}<\/pre>\n
The updated code is available on GitHub<\/a>.<\/p>\n
The movecount()<\/em> function isn’t just for reporting the output, as shown in Figure 1. No, it comes in handy as the code progresses. The goal is to determine which of the valid squares the knight can move to based on the number of next moves possible. This topic is tackled in next week’s Lesson<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
If the knight on a chessboard moved in a traditional way (horizontally or vertically), plotting its moves would be a cinch. Alas, that’s just not the case. 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-5628","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\/5628","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=5628"}],"version-history":[{"count":6,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/5628\/revisions"}],"predecessor-version":[{"id":5658,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/5628\/revisions\/5658"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5628"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5628"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5628"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Literal KM<\/code> equals the number of potential knight moves, set to eight. The moves are defined in the position<\/em> structure pairs<\/code> as row and column offsets. This topic was discussed in an earlier lesson<\/a>.<\/p>\n