Thread: Structs

Hey, I have studied the subject of structs.
when I make a struct it's a general abstract concept until I make a variable of concrete type of that struct then it will allocated in the memory.
To be more explicit for me, can someone please give me an analogous of real life which is visualizing the concept of "structs" and its allocations in the memory once declaring its variables?!



Moreover, what happened when I write the same name in two concrete structs, meaning lets assume I have defined struct called "struct BOOK" , and write like this :
struct BOOK b1 = {something};
struct BOOK b1= {something different} ; so the computer will allocate for me b1 and put it's value as {something} and after being called once again struct BOOK b1={something different} ; he will go to the name b1 that's already defined previously, and put the updated value or .. ? or totally he's not allowing similarity in names(same names)?!

thanks in advance !

1. Blueprint.

2. That's a stupid question. You should have written a program to find out for yourself. If after you observed the result of compiling that program, you wanted to check that your conclusion was correct, then that would be a smart question.

1. You know what a blueprint is but you can't see the obvious analogy? A struct is to a variable as a blueprint is to a house. A blueprint/struct tells you how to make a house/variable. From one blueprint/struct can be made many houses/variables. (BTW, only retards ask for analogies.)

2. You have 436 posts and you still don't know that you can't have two variables with the same name in the same scope? Are you capable of learning anything? At all? Ever? Stop trolling. Post complete programs. Prove you are not a retard.

And you apparently already knew what a struct is for. You didn't need an analogy in the first place, which is why I decided a one-word answer was generous.

What did you expect as a reply for #2 anyway? Didn't the compiler answer your question?