An object oriented program may be viewed as a collection of interacting objects, as opposed to the conventional model, in which a program is seen as a list of tasks (subroutines) to perform. In OOP, each object is capable of receiving messages, processing data, and sending messages to other objects. Each object can be viewed as an independent "machine" with a distinct role or responsibility. Actions (or "methods") on these objects are closely associated with the object. For example, OOP data structures tend to "carry their own operators around with them" (or at least "inherit" them from a similar object or class) — except when they must be serialized. ----- Wikipedia
Some programmer do it this way but that is not the idea behind a class. classes try to implement the concept of OOP.
but yes sometimes it is only that what you said...
Alright. Thanks for your help. I'll go take a look at some examples of classes and hopefully i'll have a better understanding of it.