Problem with definitions and executable statements

[bluechip]

I wrote a program to calculate the tranpose of a matrix. The declaration part of my code is

int m, n; //m is the number of rows of the array and n is the number of columns of the array
int i,j;
printf("What is the order of the matrix. Input number of ROWS and COLUMNS: ");
scanf("%d%d",&m,&n);
int number[m][n];
int transpose[n][m];

I didnt want to use fixed integers in the arrays because I wanted the user to specify the order of the matrix.
The program worked well in CodeBlocks 10.05 which is the IDE I use, but when I tried to run it in Turbo C++, the program gave me an error, "Constant Expression required in function main" and the int number[m][n] line was highlighted.
Can anybody kindly explain to me why the program didnt run in Turbo C++ but worked in CodeBlocks.
I'm new to C programming, just over a month old. Thank you!

[laserlight]

The program worked well in CodeBlocks 10.05 which is the IDE I use, but when I tried to run it in Turbo C++, the program gave me an error, "Constant Expression required in function main" and the int number[m][n] line was highlighted.
Can anybody kindly explain to me why the program didnt run in Turbo C++ but worked in CodeBlocks.

Because on these two lines, you create variable length arrays:

int number[m][n];
int transpose[n][m];

The VLA feature was only introduced in the 1999 edition of the C standard (C99), so your older compiler presumably does not provide it.

By the way, CodeBlocks is an IDE. You are probably using gcc.

[bluechip]

Because on these two lines, you create variable length arrays:

int number[m][n];
int transpose[n][m];

The VLA feature was only introduced in the 1999 edition of the C standard (C99), so your older compiler presumably does not provide it.

By the way, CodeBlocks is an IDE. You are probably using gcc.

Thank you very much for your response.

[Adak]

I used Turbo C/C++ ver. 1.01, and what Laserlight said was accurate for that version.

Have you tried using

const int variableName;

yet? That wouldn't work with 1.01 that I had, but would be worth a try with other versions.

You don't like using r and c variable names for ROWS and COLS?