M$ Explaination

• • Reply

  18 years ago

  by vanja

  vanja

  , United States

  Joined 18 years ago

  The VarPtr, ObjPtr, StrPtr, VarPtrArray, and VarPtrStringArray functions in Visual Basic 6.0 were undocumented and unsupported functions that could be used to return a pointer to a memory address. Although unsupported, these functions were sometimes used when working with Windows API calls that would have otherwise been inaccessible from Visual Basic.
  

  
  These functions are not supported in Visual Studio .NET; however, most of the scenarios where they were used can be addressed through new functionality in the .NET Framework. Many of the Windows API calls that were necessary in Visual Basic 6.0 are now encapsulated in the framework; pointer references are no longer necessary.
  

  
  Look at that explaination..True Lies..No longer necessary?To whome?

  Report abuse
• • Reply

  18 years ago

  by vanja

  vanja

  , United States

  Joined 18 years ago

  When you choose the type of your object, the choice of where the object
  will be created is implicit. Simple types (ints, doubles, and longs) are always
  created on the stack (unless they are contained within other objects), and
  classes are always created on the heap. You cannot control where on the heap
  an object is created, you can't get its address, and you can't pin it down
  in a particular memory location. (There are ways around these restrictions,
  but they take you out of the mainstream.)
  

  
  

  
  OH YEAH??? "Good night story"

  Report abuse