   Stuff I dont get in C# yet...some help maybe?
  The "get/set" accessorsOverrideBoxing/UnboxingOperator OverloadingA practical use for a structCastingI''m really only half way through my book yet, I was hoping for some sites that offer a more class room like approach to learning.  Like assignments give and such.Any help is GREATLY appreciated.  Or if you can simplify some of these concepts for me here, that will work too. 
  Specifically overriding.  That confuses the hell out of me. ;  It''s a little hard to give answers because you don''t specify what exactly you don''t understand.quote:Original post by benutne  The "get/set" accessorsSuppose you have a private variable (say int Age in your class. You can write two methods to access it (GetAge and SetAge) or you could use get/set accessors instead. This is essentially the same thing except if you use get/set accessors you get a nicer syntax (you can access Age as if it was a public variable while in reality you can do all kinds of processing in your get/set accessors like grabbing the value out of the database).quote:Original post by benutne  OverrideIf you have two classes (one derived from the other) and both have a virtual function Func(), you use the keyword override. This is done to ensure that your derived class really intends to override the base Func(), as opposed to adding a virtual function Func() without being aware of Func()''s existance in the base class (which could lead to a whole bunch of problems).quote:Original post by benutne  Boxing/UnboxingBoxing/unboxing allows you to "wrap" value types in objects and back. For instance when you try to store an integer or a float in a Hashtable, you implicitly use boxing and unboxing (compiler does it for you). You don''t need to worry about it much at this point. After you become more proficient in C# you can back to understand boxing/unboxing and performance penalties that are associated with them. BTW, once generics are introduced to C#, boxing/unboxing will be even less of an issue they are now.quote:Original post by benutne  Operator OverloadingThat''s a fairly large topic. What exactly don''t you understand about it?quote:Original post by benutne  A practical use for a structIf I was implementing matrix or vector functionality, I''d use a struct. Read on about the tradeoffs associated with the whole struct/class thing.quote:Original post by benutne  CastingIf you have no prior experience with object oriented languages this might be a little hard to grasp. Read on, young Jedi.;  Structs are value types, classes are reference types.   quote:Original post by bishop_pass  The burden for the thread closure falls on you, Reindeer Effect.;  Good.  All good.  I guess I understand casting...jsut need some good examples for using it.  And I dont really understand overloading and overriding very well.  Correction...I understand them, I''m just not adept at using and recognizing them.   