Variant type

Variant is a data type in certain programming languages, particularly Visual Basic and C++ when using the Component Object Model.

In Visual Basic (and Visual Basic for Applications) the Variant data type is a tagged union that can be used to represent any other data type (e.g. integer, floating-point, single- and double-precision, object, etc.) except fixed-length string type. In Visual Basic any variable, not declared explicitly or the type of which is not declared explicitly, is taken to be a variant.

While the use of variants in general (and especially of not explicitly declared variants in the case of Visual Basic) is not recommended, they can be of use when the needed data type can only be known at runtime, when the data type is expected to vary, or when optional parameters and parameter arrays are desired.

Among the major changes in Visual Basic .NET, being a .NET language, the variant type was replaced with the .NET "object" type. There are similarities in concept, but also major differences, and no direct conversions exist between these two types. For conversions, as might be needed if Visual Basic .NET code is interacting with a Visual Basic 6 COM object, the normal methodology is to use .NET marshalling.

In unrelated usage, "variant type" is also used to refer to algebraic data type, whose constructors are often called "variants".

Format

A variable of variant type, for brevity called a "variant" needs 16 bytes storage and its layout is as follows:

Examples

In Visual Basic, a variant named A can be explicitly declared as shown in these two examples:Dim ADim A as VariantIn C++, a variant named A can be declared as follows:VARIANT A;

Types

A few examples of variants that one can encounter in Visual Basic follow. In other languages other kinds of variants can be used as well.
*¹ The type of an uninitialized variant.
*² The type of a NULL value in a database, i.e. not uninitialized, nor equivalent to a C++ null pointer.
*³ The actual TypeName for missing arguments is Error.
*⁴ The data would be a BSTR.
*⁵ The object type set to a null reference.
*⁶ TypeName will return the name of the class of the object contained. The data would be an interface pointer, i.e. a pointer to a pointer to the first in an array of function pointers.

Common uses

Collections

The Collection class in OLE Automation can store items of different data types. Since the data type of these items cannot be known at compile time, the methods to add items to and retrieve items from a collection use variants. If in Visual Basic the For Each construct is used, the iterator variable must be of object type, or a variant.

Dispatch method calls

In OLE Automation the IDispatch interface is used when the class of an object cannot be known in advance. Hence when calling a method on such an object the types of the arguments and the return value is not known compile time. The arguments are passed as an array of variants and when the call completes a variant is returned.

Optional parameters

In Visual Basic a procedure argument can be declared to be optional by prefixing it with the Optional keyword. When the argument is omitted Visual Basic passes a special value to the procedure, called "Missing" in the table above, indicating that the argument is missing. Since the value could either be a supplied value or a special value, a variant must be used.Function GetText(Optional ByVal Index) As String If IsMissing(Index) Then GetText = Item(CurrentItem) Else GetText = Item(Index) End IfEnd FunctionSimilarly the keyword ParamArray can be used to pass all following arguments in a variant array.