Strange warning in a C function const multidimensional-array argument

by

I believe the problem is the constraints specified in C99 6.5.16.1(1), which seem to prohibit mixing qualifications in assignments, except for pointers for which an inclusive-qualifier exception is defined. The problem is that with indirect pointers, you end up passing a pointer to one thing to a pointer to another. The assignment isn’t valid because, if it was, you could fool it into modifying a const-qualified object with the following code:

const char **cpp;
char *p;
const char c="A";
cpp = &p;  // constraint violation
*cpp = &c; // valid
*p = 0;    // valid by itself, but would clobber c

It might seem reasonable that cpp, which promises not to modify any chars, might be assigned a pointer to an object pointing at non-qualified chars. After all, that’s allowed for single-indirect pointers, which is why, e.g., you can pass a mutable object to the second parameter of strcpy(3), the first parameter to strchr(3), and many other parameters that are declared with const.

But with the indirect pointer, at the next level, assignment from a qualified pointer is allowed, and now a perfectly unqualified pointer assignment will clobber a qualified object.

I don’t immediately see how a 2-D array could lead to this situation, but in any case it hits the same constraint in the standard.

Since in your case, you aren’t actually tricking it into clobbering a const, the right thing for your code would seem to be inserting the cast.

Update: OK guys, as it happens this issue is in the C faq, and this entire discussion has also taken place several times on the gcc bug list and on the gcc mailing list.

The lesson: you can pass a T *x when const T *x is expected, by explicit exception, but T *x and const T *x are still distinct types, so you can’t pass a pointer to either one to a pointer to the other.

More Related Contents:

  1. Passing multidimensional arrays as function arguments in C
  2. Manipulate multidimensional array in a function
  3. How to return matrix (2D array) from function? (C)
  4. Unspecified number of parameters in C functions – void foo()
  5. How can I malloc a struct array inside a function? Code works otherwise
  6. Procedure to include own functions to ANSI C Standard library
  7. Sum of the all the numbers between a and b [closed]
  8. “static const” vs “#define” vs “enum”
  9. Is 2d array a double pointer? [duplicate]
  10. Can we change the value of an object defined with const through pointers?
  11. Why does a C-Array have a wrong sizeof() value when it’s passed to a function? [duplicate]
  12. Function pointers and address of a function
  13. What are the arguments to main() for?
  14. Why do we need to specify the column size when passing a 2D array as a parameter?
  15. Pointer address in a C multidimensional array
  16. In C, can a const variable be modified via a pointer?
  17. Where are constant variables stored in C?
  18. Can I set a default argument from a previous argument?
  19. Malloc a 3-Dimensional array in C?
  20. const usage with pointers in C
  21. Changing array inside function in C
  22. Should useless type qualifiers on return types be used, for clarity?
  23. How to dynamically allocate a contiguous block of memory for a 2D array
  24. How can I work with dynamically-allocated arbitrary-dimensional arrays?
  25. No defined type of a function parameter defaults to int? Am I insane?
  26. What is the difference between static const and const?
  27. Why can’t I pass constant arrays as arguments?
  28. How can I create C header files [closed]
  29. In C, what is the difference between `&function` and `function` when passed as arguments?
  30. 2D Array indexing – undefined behavior?

Leave a Comment