Pointer to array with const qualifier in C & C++

by

GCC-gnu

In GNU C, pointers to arrays with qualifiers work similar to pointers to other qualified types. For example, a value of type int (*)[5] can be used to initialize a variable of type const int (*)[5]. These types are incompatible in ISO C because the const qualifier is formally attached to the element type of the array and not the array itself.

C standard says that (section: §6.7.3/9):

If the specification of an array type includes any type qualifiers, the element type is so- qualified, not the array type.[…]

Now look at the C++ standard (section § 3.9.3/5):

[…] Cv-qualifiers applied to an array type attach to the underlying element type, so the notation “cv T,” where T is an array type, refers to an array whose elements are so-qualified. An array type whose elements are cv-qualified is also considered to have the same cv-qualifications as its elements. [ Example: 

 typedef char CA[5];
 typedef const char CC;
 CC arr1[5] = { 0 };
 const CA arr2 = { 0 };

The type of both arr1 and arr2 is “array of 5 const char,” and the array type is considered to be const- qualified. —endexample]

Therefore, the initialization 

const int (*p2)[9] = &array;

is assignment of type pointer to array[9] of int to pointer to array[9] of const int. This is not similar to assigning int * to a const int * where const is applied directly to the object type the pointer points to. This is not the case with const int(*)[9] where, in C, const is applied to the elements of the array object instead of the object the pointer points to. This makes the above initialization incompatible.

This rule is changed in C++. As const is applied to array object itself, the assignment is between same types pointer to const array[9] of int instead of type pointer to array[9] of int and pointer to array[9] of const int.

More Related Contents:

  1. What is the difference between '.' and '->' when used in array? [closed]
  2. Why is sizeof giving incorrect number of bytes in C++?
  3. Something went wrong with passing pointer to a function
  4. Passing a 2D array to a C++ function
  5. Why isn’t it legal to convert “pointer to pointer to non-const” to a “pointer to pointer to const”
  6. determine size of array if passed to function
  7. May I treat a 2D array as a contiguous 1D array?
  8. Why does cout print char arrays differently from other arrays?
  9. C++ pass an array by reference
  10. Address of an array
  11. Does const-correctness give the compiler more room for optimization?
  12. May I take the address of the one-past-the-end element of an array? [duplicate]
  13. A pointer to 2d array
  14. C++ correct way to return pointer to array from function
  15. Store an int in a char array?
  16. Pointer-to-pointer dynamic two-dimensional array
  17. How to get the real and total length of char * (char array)?
  18. C++ typedef interpretation of const pointers
  19. Modifying a const int in C++ [duplicate]
  20. Pointer interconvertibility vs having the same address
  21. Are non dereferenced iterators past the “one past-the-end” iterator of an array undefined behavior?
  22. Pointer to array of unspecified size “(*p)[]” illegal in C++ but legal in C
  23. C++: Why is const_cast evil?
  24. Returning non-const reference from a const member function
  25. array decay to pointer and overload resolution
  26. array of pointers as function parameter
  27. Function returning array but main showing garbage [duplicate]
  28. Use const wherever possible in C++?
  29. difference between pointer to an array and pointer to the first element of an array
  30. int *array = new int[n]; what is this function actually doing?

Leave a Comment