First of all, the row and column are arbitrary properties of an array. You decide what you call a row and what you call a column.
If I want to declare a two dimensional array in C, I could do something like this:
So we're playing chess here. 8 x 8 board. But is the first number a row or a column? Well, there is no good answer. No wrong either. It's totally up to you. As long as you handle things consistently, it doesn't matter. You can call the first index row or the second. The decision is yours.
If I'd use the first index to be the row information and the second to be the column information, then I would access the chess piece on the board in row 2 column 5 (column E if you're an avid chess player) like this:
board = Pawn;
And there you go, there is now a Pawn on row 2 column 5. Please note that I used 1 and 4 respectively as indices are 0-based in C (and many other programming languages) while in mathematics (and real life problems), we typically use 1-based indexing.
Again, I could have chosen to have the first index the column and the second to be the row. As long as I keep to my rules, all is fine.
Even I can index a one dimensional array as if it would be a two dimensional:
#define ROW_SIZE 8
#define COLUMN_SIZE 8
ChessPiece board[ROW_SIZE * COLUMN_SIZE];
ChessPiece GetChessPiece(unsigned int row, unsigned int column)
return board[row * COLUMN_SIZE + column];
void SetChessPiece(unsigned int row, unsigned int column, ChessPiece piece)
board[row * COLUMN_SIZE + column] = piece;
for (int row = 0; row < ROW_SIZE; row++)
for (int column = 0; column < COLUMN_SIZE; column++)
switch (GetChessPiece(row, column))
case Empty: printf("."); break;
case Pawn: printf("P"); break;
case Rook: printf("R"); break;
case Knight: printf("N"); break;
case Bishop: printf("B"); break;
case King: printf("K"); break;
case Queen: printf("Q"); break;
default: printf("?"); break; // error case
//board = Pawn;
SetChessPiece(1, 4, Pawn);
Note: It doesn't mean you should use one dimensional arrays always. :) This is just to show that rows and columns are really the decisions of the programmer.