Things that Dangle…

C Programming Structure and Pointer

Posted in Technology By Danlie

Presently how about we speak somewhat about how to pass these structs around to different functions and stuff. I specified before that you presumably need to pass a pointer to the struct rather than the struct itself. Why?

Don’t you despise it when the teacher makes an inquiry like that, however you’re excessively drained in address, making it impossible to want to start to consider it? “Simply let me know and we’ll get on with it,” is what you’re considering, isn’t it.

Fine! Be that way! Indeed, recall that when you pass parameters to functions, and I’ll make a sound as if to speak here in readiness to say once more, every parameter without fail gets

when you call a function! So in the event that you have a colossal struct that is similar to 80,000 bytes in size, it will duplicate that onto the stack when you pass it. That requires some investment.

Rather, why not pass a pointer to the struct? I hear you- – doesn’t the pointer need to get duplicated on the stack then? Beyond any doubt does, however a pointer is, nowadays, just 4 or 8 bytes, so it’s much simpler on the machine, and works quicker.

Furthermore, there’s even a tiny bit of syntactic sugar to get to the fields in a pointer to a struct. For those that aren’t mindful, syntactic sugar is a component of a compiler that streamlines the code despite the fact that there is another approach to finish the same thing. For example, I’ve as of now specified the += various times…what does it do? Did I ever let you know? To be completely forthright, in all the fervor, I’ve overlooked myself. Here is a case that shows how it functions like another two administrators, yet is a smidgen simpler to utilize. It is syntactic sugar:

i = i + 12; i += 12;

You see? It’s not an important administrator in light of the fact that there’s another approach to do likewise, yet individuals like the alternate route.

Be that as it may, we are misguided course, buster. I was discussing pointers to structs, and here we are discussing how to get to them. Here’s a sample wherein we have a struct variable, and another variable that is a pointer to that struct sort, and some utilization for both (this will utilize struct stuff from above

#include <stdio.h> struct i { int j; float k; }; int main(void) { struct i x; struct i *y; y = &x; x.j = 3490; (*y).j = 3491; y->j = 3491; return 0;}

So here we’ve seen two or three things. For one, we have the way with which we deference a pointer to a struct and afterward utilize the spot administrator (.) to get to it. This is somewhat the great method for doing things: we have a pointer, so we deference it to get at the variable it focuses to, then we can regard it as though it is that variable.


In any case, syntactic sugar to the salvage, we can utilize the bolt administrator (- >) rather than the dab administrator! Spares us from looking revolting in the code, doesn’t? The bolt administrator has a work in regard, so you don’t need to upset that language structure when you have a pointer to a struct. So the principle is this: on the off chance that you have a struct, utilize the dab administrator; in the event that you have a pointer to a struct, utilize the bolt administrator (- >)

Leave a Reply:

Your email address will not be published. Required fields are marked *