A really noob question but I thought that I should find the answer to it in any case.
There was always much noise made about JAVA's inherent speed and some of that speed being attributed to the inbuilt so called garbage collection. Having learned first to program in JAVA at uni I am now developing a program in VB 6. I saw somewhere in my wonderings through the web (might have even been in this forum) that you should set your objects to nothing when you are done "otherwise you will really hate yourself".
This is like wiping the counter after making a sandwich I guess. I would like to know if that is really true of VB and in what circumstances it would apply.
Should it only be objects as a sort of de-constructor or should one for instance have each sub setting all the local variables it created to "nothing" before the sub/function ends?
Thanks to anyone who doesn't mind pointing me in the right direction with regard to this.