GivenRandy
asked on
To Use Call() or Not to Use Call()
In VB.NET, using Call() is not required when call functions. However, what are good reasons to use Call() and good reasons not to use Call()?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It really boils down to this: Real men use call, sissies don't.
@Joe_Griffith:
Thems fightin' words :)
Bob
Thems fightin' words :)
Bob
You said it Joe_Griffith. LOL!
Damn! I belong to the sissies! ;)
<Quote movie="Magnum Force">
A man's got to know his limitations.
</Quote>
Bob
A man's got to know his limitations.
</Quote>
Bob
lol @Bob
ASKER
Personally, I haven't used Call() in probably a decade. I prefer to not clutter things with extra text and with VB.NET it is even less useful (like pointed out above). I asked because I have seen a resurgence of the Call() recently in books and magazines. I was confused as to why that was and I thought maybe I was missing something. ;)