Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Structures
- Thread starter elziko
- Start date
Hi Elziko!
Think of a structure as a lightweight class.
It's a value type (memory comes from the stack), whereas a class is a reference type (the pointer to the class comes from the stack, but memory for the guts of the class come from the heap).
While you can add methods and such to a structure, I myself don't see that as a good use. I prefer to think of a structure as a simple place to hold a small amount of data. If I need to manage a large amount of data (like, for a customer), or need nested data (Invoice + it's detail lines), then I'd use a class.
Chip H.
Think of a structure as a lightweight class.
It's a value type (memory comes from the stack), whereas a class is a reference type (the pointer to the class comes from the stack, but memory for the guts of the class come from the heap).
While you can add methods and such to a structure, I myself don't see that as a good use. I prefer to think of a structure as a simple place to hold a small amount of data. If I need to manage a large amount of data (like, for a customer), or need nested data (Invoice + it's detail lines), then I'd use a class.
Chip H.
- Status
Similar threads
- Locked
- Question
