Length of array in function argument

by

sizeof only works to find the length of the array if you apply it to the original array.

int a[5]; //real array. NOT a pointer
sizeof(a); // :)

However, by the time the array decays into a pointer, sizeof will give the size of the pointer and not of the array.

int a[5];
int * p = a;
sizeof(p); // :(

As you have already smartly pointed out main receives the length of the array as an argument (argc). Yes, this is out of necessity and is not redundant. (Well, it is kind of reduntant since argv is conveniently terminated by a null pointer but I digress)

There is some reasoning as to why this would take place. How could we make things so that a C array also knows its length?

A first idea would be not having arrays decaying into pointers when they are passed to a function and continuing to keep the array length in the type system. The bad thing about this is that you would need to have a separate function for every possible array length and doing so is not a good idea. (Pascal did this and some people think this is one of the reasons it “lost” to C)

A second idea is storing the array length next to the array, just like any modern programming language does:

a -> [5];[0,0,0,0,0]

But then you are just creating an invisible struct behind the scenes and the C philosophy does not approve of this kind of overhead. That said, creating such a struct yourself is often a good idea for some sorts of problems:

struct {
    size_t length;
    int * elements;
}

Another thing you can think about is how strings in C are null terminated instead of storing a length (as in Pascal). To store a length without worrying about limits need a whopping four bytes, an unimaginably expensive amount (at least back then). One could wonder if arrays could be also null terminated like that but then how would you allow the array to store a null?

More Related Contents:

  1. Pointers program
  2. Are there differences between pointers to object stored on stack and heap? [closed]
  3. With arrays, why is it the case that a[5] == 5[a]?
  4. Pointer Arithmetic [closed]
  5. What is the difference between char array and char pointer in C?
  6. How do I understand complicated function declarations?
  7. How can I allocate memory and return it (via a pointer-parameter) to the calling function?
  8. Pointer Arithmetic In C
  9. Why can’t I cast a function pointer to (void *)?
  10. C pointers : pointing to an array of fixed size
  11. Array to pointer decay and passing multidimensional arrays to functions
  12. Can the size of pointers vary between data and function pointers?
  13. Why does this code segfault on 64-bit architecture but work fine on 32-bit?
  14. C: Which character should be used for ptrdiff_t in printf?
  15. What is guaranteed about the size of a function pointer?
  16. Why doesn’t scanf need an ampersand for strings and also works fine in printf (in C)?
  17. How to print variable addresses in C?
  18. Returning Arrays/Pointers from a function
  19. why is array name a pointer to the first element of the array?
  20. C – Accessing data AFTER memory has been free()ed?
  21. allocate matrix in C
  22. Passing two-dimensional array via pointer
  23. Getting the size of a malloc only with the returned pointer
  24. Why can I change the value of a const char* variable?
  25. Mis-aligned pointers on x86
  26. How to find the size of an array (from a pointer pointing to the first element array)?
  27. Can I treat a struct like an array?
  28. Can a “container_of” macro ever be strictly-conforming?
  29. Pointer comparisons in C. Are they signed or unsigned?
  30. Difference between pointer to pointer and pointer to array?

Leave a Comment