Help! Using dynamic allocation and malloc

I have to use dynamic memory allocation to return a newly-created array from a
function. The return value cannot be a “dynamic array” (created by an ordinary
array declaration), because such an array cannot safely be accessed from outside the function
where it was declared. Memory space obtained from the malloc() function, however, can be
passed around from one function to another. The cost of this freedom is that you need to be
more careful with this explicitly allocated space; for example, you have to call free() when
you’re finished with it.


REQUIREMENTS
• You must call malloc() to create the space for the new array returned by your function.
• You must call free() in your main() function to release the space when you have
finished using it.


PROBLEM
Write a function with this prototype:
double *rowmaxes(int N, double matrix[N][N]);
Rowmaxes() must return a new array containing in element i the largest element in row i of the
N×N matrix called matrix.
In the same file as your function, write a program (a main() function) that asks the user for
whatever input is needed to try out the function. Print the results. Don’t forget to free the
memory allocated in your function.

Help pleaseeee!

Read our forum guidelines and homework policy.

Give it a shot, post your code in code tags, and explain where you're stuck. Then you'll get some help.

What have you done so far?

An aside for the seasoned C programmers: Is it even possible to define a prototype with unknown dimensions of the array? Especially if the N parameter is determined during run-time, and the width of the matrix is dynamic on that basis. The compiler would not know how to calculate row offset.

C99 allows arrays of variable length. I believe the only requirement for parameters in this regard is that the parameter giving the length (N in this case) come before the array in the parameter list.

Awesome! I'll have to play with that. That means the compiler is generating code which calculates offsets on-the-fly rather than hard-coding them. Could come in handy if it's faster executing than linearizing arrays and doing the index calculations manually especially for multi dimensional arrays.