array vs &array Pointers Difference Explained | C Programming Tutorial 

This video is a must-watch for any C programmer. The concept of arrays vs pointers, the decaying of arrays into pointers and how everything is handled in memory is crucial in understanding C.

This guy is an absolute legend. Just when i though i had mastered pointers, the concept manages to leave me bamboozled again. Thank you for your amazing work! ❤

Your programming language tutorials are one of best on YT, amazing job!

This is the first channel I look at when there is something I don't understand about the subject.I can find everything I'm looking for, even what I'm not looking for 😄. Thank you for such valuable information. 😊

really good video. really helpful how you formatted the print statements so that everything was in line. You do the small things really well.

Every small detail about c is crystal clear here in this channel..Keep it up bro...

Mr. all of your videos are 100% understandable unlike lecturers at my university. well done !

passed all the morning watching videos on array dacay on other guys' "famous" channels, BUT your explainations are ALWAYS the best, precise, concise, starting from scratch and working up. GREAT WORK!

With just this one video, you throw a clear examole of an" ideal teacher with a great depth of knowledge about every single concept".Sir,PLEASE PLEASE MAKE a Playlist for DSA as it is absolutely crucial and difficult. A teacher like you ought to teach such critical concepts,kindly understand. Thank you soooo much for the videos and hope you do a dsa course for us needy.

Your explanation is the best explanation I've ever seen. I grasped so many things from your videos and I am still watching them; thanks a million Dr Kevin.

Been a minute since I’ve worked with memory/C, this was immensely helpful and probably saved countless hours. Thanks!

I think this videos is showing the differences between arrays and pointers in C quite well. It also gets real quirky when you add memory areas you got with malloc and treated like an array to the mix

I've spent days trying to find a resolution to my confusion, in differentiating 'array' and '&array'. This video was extremely helpful, subbed.

I love your videos going full c and your videos help me so much to understand these tricky concepts. Thanks again 🙏

Thank you for sharing knowledges and source code!

AWESOME!!!! Please, keep doing this kind of videos! Thank you!!!

These videos deserve a lot more views. They are really good. Thanks.

Very interesting explanation. I studied C very long years ago, your videos are great refresh to details many programmers don't pay attention to. Thank you Kevin.

the pointer arithmetic side of arrays are so cool, and your video just made it better!

I made some tests about pointers and pointers to an entire array, and I found that if you dereference a pointer to an entire array like a int (*)[5], it will obtain a pointer int * to the first element on this array pointer. So that's why in 11:00 momment was printed an adress. To get the correct behaviour, you need to add an extra dereference operator *, and the line will be: printf(" **(matrix[1] + 1): %zu ", **(matrix[1] + 1)); So the dereference order stays: int (*)[5] -> int * -> int Which is similar to: int ** -> int * -> int But the int ** and int (*)[5] types aren't interchangeable Curiosity: The names of a N-Dimensional matrix decay to pointers to an entire first (N-1)-Dimentional Array of the N-Dimensional Array, excluding the n = 1 case. Then we have: int array1[5]; //1D int array2[5][5]; //2D int array3[5][5][5]; //3D Therefore: array1 decays to a int * to the first element. This case is exclusive to the rule. array2 decays to a int (*)[5] to the first row of the matrix, and a row is a 1D array. array3 decays to a int(*)[5][5] to the first 2D matrix of the 3D matrix. Another Curiosity: If you use the reference operator & in a matrix instead of either a matrix row or in a vector, you will obtain a pointer to an entire matrix, and the type stays something like int (*)[3][5], and the order of the dereference stays: int (*)[3][5] -> int(*)[5] -> int * -> int And the detail is that these operations, all of them, returns the first element, row or matrix of the array referenced. Then if I have a 3D multidimensional like this: int matrix[5][5][5]; &matrix -> pointer to the entire 3D matrix &matrix[0] -> pointer to the FIRST 2D matrix in the 3D matrix &matrix[0][0] -> pointer to the FIRST ROW in the FIRST 2D matrix in the 3D matrix &matrix[0][0][0] -> pointer to the FIRST ELEMENT in the FIRST ROW in FIRST 2D matrix in the 3D matrix.

simply brilliant, these questions are asked in interviews to check proficiency of the candidate in pointers

Bravo dude! You have a gift for teaching so clearly. I was just looking at the main function second parameter this morning, how you can write char *argv[] or char **argv, and I couldn't get it...but watching this made it click. Thank you!

Excellent video, thank you so much!

amazing, thank you very much for this fantastic video.

All videos are great! But this one solved one of the problem I struggle to understand always :) Thanks.

your videos are clear and with good examples. thank you sir

Thank you very much for this thorough explanation, you provided an invaluable insight, and I'm very grateful for it

I’m glad I found your course and videos. But wonder I nearly failed C lo those many decades ago.

very good explanation thanks for your helpful videos

Wow, such a great explanation 🎉

good and useful points. nice clean method of presenting essential topics.

i mean this is what i was exactly looking for , thank u so much ❤

terrific instructor

This guy is a legend greeting from England ❤

Nice!👍👍👍

Great video! Thanks!

THANK YOU SIR!

Thanks Dr kevin, well explained as usual , the term 2D array makes it more complex to understand I like to break it like this : matrix[3][5] is an array of 3 elements of type int[5], now I can see how can I declare a pointer of type int[5] (or pointing to an element of type int[5]) that will point of the first element of matrix, int (*pointer_matrix)[5] = matrix ; same as ----- > int (*pointer_matrix)[5] = &matrix[0] ; if I do something like this : int(*pointer_matrix)[5] = matrix[0] ; it will be wrong because matrix[0] will be decayed into a pointer of type (int*) instead of (int(*)[5] ) it gets more complex with functions 🙃🙃.

best of luck keep going

There are very few concepts you need to understand to master pointers. Most important is understanding 'type of pointer'.

Love it 😍

You are a god teacher man I love you

nice pls post more finding.

Wow will I ever need to use it?

So that's pretty much useful to calculate the size of the array.

Pointer arithmetic was Ritchie's biggest mistake. In general C keeps things simple as it should . But in the case of pointer arithmetic it's trying to be too "helpful" so that you don't have to be explicit as a coder. That just makes it confusing: if "+1" just meant "add one" all this confusion would go away. KISS, Dennis. KISS!

It is perhaps worth mentioning that sizeof is a function where this decay of array pointers don’t happen.

Thank you making this video! Everything regarding arrays/pointers makes way more sense now. However, I am trying to replicate what you have discussed on one of my Ubuntu VMs using VSCode. I am running into a format error in which my compiler is saying that %zu expects an argument of type size_t. I know I can just use %p to see the hex, however, I would like to see the decimal notation as you have shown in the video. Any recommendations/suggestions? Thanks!

Nice video! One humble request, re 8:07: I'd love it if you'd use the term parentheses here, and save the word brackets for specifically the [] characters. I know it sometimes also gets used to just talk about the idea of bracketing something in something else, and thus can apply to (), {}, [], and even ... I just find that it nice to call those parentheses (or "round brackets"), braces ("curly brackets"), brackets ("square brackets'), and chevrons ("angle brackets"), and keep things specific. Again, you're not wrong, just a humble request.

Great

Let’s go!!!

My compiler - gcc on Ubuntu - says I should use %ls instead of %zu, but then when I use it it just does not print the address. Very odd, nio idea what is going on. I do can make it work with %ld but also get the same warning as with &zu.

thanks for this Video :) in order to make peace with douple pointer 😅 can you just please make a video about douple Pointer and espicially descripe how to use douple pointer in oeder to creat an array of Strings!! :)

Sir, please make a video on function pointer as member of array of structures

Hey man quick question what IDE do you use I see a lot of youtubers use it.

why when we do sizeof(array) it returns the (byte of int )*number of elements if it is the pointer of the first element why it did not return just 4 byte all of the time

Please sir, do you have some examples about : pointer to an array VS pointer to a pointer, when and how to use this particular pointer if we want to find for example the size of the array ... I 'm confused and wanted to clarify this point please... (why sometime we write **ar and not *ar[] espacially when the size of the array is dynamically allocated. I thing this is why in the main function we have main(int argc, char *argv[]) Thanks !

What about char *argv[]? Array of pointers to char with indefinite size.

ti (the instrunt into the channel rack) and then it crashes the soft soft... Can soone help please?

13:22 what if the statement modified as "int *pointer[5] = &matrix[1] + 1;" ? & the warning will go away or not?

My gcc compiler warns me against the use of %zu (expects a size_t type)

Int arr[10]; Int *ptr; Is ptr=arr,ptr=&arr and ptr=&arr[0] same ?

Great video, but one thing is confusing to me. I know that array and &array don't refer to the same thing, but why does array == &array??? Correct me if I'm wrong but, array == &array is saying that the value of array is equal to its location in memory.

I would expect matrix[1] to point to the second row and matrix[1][0] to point to the first element of the second row of matrix. Why does matrix[1] decay to matrix[1][0] ? Doesn't seem logical since clearly the second element in matrix is a row, not a value inside that row.

we need the difference b/n p[] and *p

Word

The pointer concept is not difficult. What makes it difficult to recognize what is what is the C syntax when it comes to pointers which is awful. Pointers are easy, the syntax is confusing.

It's called an address operator, not an and operator

I like C but this stuff was such a mistake

I'm too later for tNice tutorials, I'll be back stoned...

The all this sh*t is not because of a flexibility of C, but because of lack of definitivity. Pointer should be an address, and increasing of an antes should always increase an address by a byte, regardless the size of array element. Because pointer is an address, no metter what data it point at. So I assume it as a problem in C. Who is no accept it and has different vision - let’s discuss.

AWESOME!!!! Please, keep doing this kind of videos! Thank you!!!