dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Visual Basic
Expertise: Beginner
Jun 1, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Set Objects to Nothing

If you set objects to Nothing, then test their nothingness, this suggestion might help you. If you declare an object as New and later set it to Nothing, VB won't set the object to Nothing. For example, if you declare an object using this code:
 
Dim oSomeObject As New SomeClass 
And later set it to Nothing using this code:
 
Set oSomeObject = Nothing
The object does terminate, but a new instance is immediately instantiated, so it appears the object hasn't been set to Nothing. You can test this by going to the Immediate window and testing '?(oSomeObject = Nothing).' It displays False. If you declare an object and explicitly set it to New, you can set the object to Nothing. For example, if you declare an object using this code, the object will be set to Nothing:
 
Dim oSomeObject As SomeClass
Set oSomeObject = New SomeClass
'.... some code ...
Set oSomeObject = Nothing
Rahuldeo S.
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date