And I have some other (related) question wich are on my mind for some time now:

Let's say I have a sub like this:

sub Bla
  dim TestObject as new cObjectClass
end sub


What will happen when I call this sub? It will initiate a new object, called TestObject of the type cObjectClass. But what after the sub has ended? Will the object stay in memory somewhere, because I didn't dispose it? Or will it be gone (and free-d memory) after the sub is done?




Next to this I'd really like to know if there are differences between the dispose-method, wich some objects have and settings the object to nothing to free the memory. So, wich way is best to free memory if you're not planning to use the object anymore?



And the last one which I don't understand:
I have two objects, let's say:
dim Human1 as new cHuman
dim Human2 as new cHuman

Now I edit Human1:
Human1.name = "Christopher"
Human1.age = 26

And then I want Human2 to be exactly as Human 1:
Human2 = Human1

Question: What do I have here now? Two different objects with both the same settings? Or one object with it's setting and the otherone pointing at the first one? In other words; if I now change the name of Human1, will it change the name of Human2 because it's a reference to the same object? Or will Human2 stay the same as before?

And is there a difference if I would have declared the humans as:
dim Human1 as new cHuman
dim Human2 as cHuman

??

Maybe there is a reference on the internet you could advise me to read about this subject?

In every case, many thanx, 'cause I really would like to know the details.

What will happen when I call this sub?

The object will be created, and a reference to it through TestObject will be created, and the reference count will be boosted to 1.
When TestObject goes out of existence, the reference count is dropped to 0. When garbage collection takes place, the memory will be reclaimed.
Because of this, you cannot rely on actions within the cObjectClass class to perform their finalizations just because the reference went away.

The Dispose method will run when the object is garbage collected, but you cannot know when that will be.
Setting to Nothing opens the door for that garbage collection, but nothing more (no pun intended).
Having or not a Dispose method makes no difference as to when the memory will be freed. If memory is needed, a GC will be triggered. This wway, the program is not slowed down by destroying objects every time they are no longer referenced, but only when memory is required.

When you run the two As New statements two objects are created, and a reference to each is created. They each have a reference count of 1.

Human2 = Human1 causes the obect that Human1 refers to to now have a reference count of 2, and causes the object that Human 2 used to refer to to now have a reference cout of 0—it can be destroyed upon GC. Human2.name = "Christopher," because it reads the same memory as was set and filled through Human1.

In your final example, the 2nd statement types the variable, but creates no object—and it does not change the size of your program. Variable names are used in compilation, but do not exist in the actual code. If an object is not created, no memory for it is ever needed.
But, accordingly, if you then refer to Human2 in code, you will recieve object or block not initialized (or whatever). You will need to either do something like Human2 = Human1, where Human 1 is an initialized object, or Human2 = New cHuman. The original statement, having typed the variable will cause a compilation error if you try Human2 = New cUberMan. That is a different type. That typing is not useless, you see. Just because it creates nothing, doesn't mean it doesn't do anything for you.

Does that clarify?

Wow! Thanx a lot for using your fine explaining skills, this realy clarifies the thing!