Printable View
Can someone explain to me the difference between both? What's the point of declaring something Private Shared instead of just Private, or even Public Shared instead of just Public? What exactly does "Shared" do, and how does it affect memory consumption? And what's up with using Private instead of Dim to declare variables outside of a method? Isn't that basically the same thing?
So many questions, such little time,
KT
I found some more information regarding this from the MSDN documentation article titled "Lifetime."
Okay, so basically a shared variable is kept in memory for the entire time the application is running? Even if the instance is disposed? Okay, now that's great if you have only one instance of the method running at a time, but what if two instances try to modify the variable at the exact same time?Quote:
Different Lifetimes
A variable declared at module level typically exists for the entire time your application is running. A nonshared variable declared in a class or structure exists as a separate copy for each instance of the class or structure in which it is declared; each such variable has the same lifetime as its instance. However, a Shared variable has only a single lifetime, which lasts for the entire time your application is running.
That really can't happen, since only one thing can happen at a time. The instance that get there first will change it, then the next instance to get there will be using the new value.
In more general term , Shared (static) variable is not specific to a class or instance , on the other hand , instance variable is specific to a class or instance .
Ok. Let's say with Shared methods for example, can I use a shared method without declaring a new instance of the class it's in? No need for New, just do:
object = class.sharedfunction(params)
?
Whaaaat.
Yes , just provide the full name of the method like this (ClassName.SharedMemberMethod) so no need for instantiation .Quote:
Originally posted by Kt3
Ok. Let's say with Shared methods for example, can I use a shared method without declaring a new instance of the class it's in? No need for New, just do:
object = class.sharedfunction(params)
?
Whaaaat.
Amazing.. Does this help with memory usage since I don't need to declare an instance of the class?Quote:
Originally posted by Pirate
Yes , just provide the full name of the method like this (ClassName.SharedMemberMethod) so no need for instantiation .
I would imagine , yes but it shouldn't be a big deal as OOP concept which is more important in consructing your classes .:rolleyes:Quote:
Originally posted by Kt3
Amazing.. Does this help with memory usage since I don't need to declare an instance of the class?