# Union type

Jump to navigation Jump to search

In computer science, a union is a value that may have any of several representations or formats within the same position in memory; that consists of a variable that may hold such a data structure. Some programming languages support special data types, called union types, to describe such values and variables. In other words, a union type definition will specify which of a number of permitted primitive types may be stored in its instances, e.g., "float or long integer". In contrast with a record (or structure), which could be defined to contain a float and an integer; in a union, there is only one value at any given time.

A union can be pictured as a chunk of memory that is used to store variables of different data types. Once a new value is assigned to a field, the existing data is overwritten with the new data. The memory area storing the value has no intrinsic type (other than just bytes or words of memory), but the value can be treated as one of several abstract data types, having the type of the value that was last written to the memory area.

In type theory, a union has a sum type; this corresponds to disjoint union in mathematics.

Depending on the language and type, a union value may be used in some operations, such as assignment and comparison for equality, without knowing its specific type. Other operations may require that knowledge, either by some external information, or by the use of a tagged union.

## Untagged unions

Because of the limitations of their use, untagged unions are generally only provided in untyped languages or in a type-unsafe way (as in C). They have the advantage over simple tagged unions of not requiring space to store a data type tag.

The name "union" stems from the type's formal definition. If a type is considered as the set of all values that that type can take on, a union type is simply the mathematical union of its constituting types, since it can take on any value any of its fields can. Also, because a mathematical union discards duplicates, if more than one field of the union can take on a single common value, it is impossible to tell from the value alone which field was last written.

However, one useful programming function of unions is to map smaller data elements to larger ones for easier manipulation. A data structure consisting, for example, of 4 bytes and a 32-bit integer, can form a union with an unsigned 64-bit integer, and thus be more readily accessed for purposes of comparison etc.

## Unions in various programming languages

### ALGOL 68

ALGOL 68 has tagged unions, and uses a case clause to distinguish and extract the constituent type at runtime. A union containing another union is treated as the set of all its constituent possibilities.

The syntax of the C/C++ union type and the notion of casts was derived from ALGOL 68, though in an untagged form.[1]

### C/C++

In C and C++, untagged unions are expressed nearly exactly like structures (structs), except that each data member begins at the same location in memory. The data members, as in structures, need not be primitive values, and in fact may be structures or even other unions. C++ (since C++11) also allows for a data member to be any type that has a full-fledged constructor/destructor and/or copy constructor, or a non-trivial copy assignment operator. For example, it is possible to have the standard C++ string as a member of a union.

Like a structure, all of the members of a union are by default public. The keywords `private`, `public`, and `protected` may be used inside a structure or a union in exactly the same way they are used inside a class for defining private, public, and protected member access.

The primary use of a union is allowing access to a common location by different data types, for example hardware input/output access, bitfield and word sharing, or type punning. Unions can also provide low-level polymorphism. However, there is no checking of types, so it is up to the programmer to be sure that the proper fields are accessed in different contexts. The relevant field of a union variable is typically determined by the state of other variables, possibly in an enclosing struct.

One common C programming idiom uses unions to perform what C++ calls a reinterpret_cast, by assigning to one field of a union and reading from another, as is done in code which depends on the raw representation of the values. A practical example is the method of computing square roots using the IEEE representation. This is not, however, a safe use of unions in general.

Structure and union specifiers have the same form. [ . . . ] The size of a union is sufficient to contain the largest of its members. The value of at most one of the members can be stored in a union object at any time. A pointer to a union object, suitably converted, points to each of its members (or if a member is a bit-field, then to the unit in which it resides), and vice versa.

— ANSI/ISO 9899:1990 (the ANSI C standard) Section 6.5.2.1

#### Anonymous union

In C++, C11, and as a non-standard extension in many compilers, unions can also be anonymous. Their data members do not need to be referenced, are instead accessed directly. They have some restrictions as opposed to traditional unions: in C11, they must be a member of another structure or union,[2] and in C++, they can not have methods or access specifiers.

Simply omitting the class-name portion of the syntax does not make a union an anonymous union. For a union to qualify as an anonymous union, the declaration must not declare an object. Example:

```#include <iostream>
#include <cstdint>

int main() {
using namespace std;

union {
float f;
uint32_t d; // Assumes float is 32 bits wide
};

f = 3.14f;
cout << "Binary representation of 3.14 = " << hex << d << endl;

return 0;
}
```

### COBOL

In COBOL, union data items are defined in two ways. The first uses the RENAMES (66 level) keyword, which effectively maps a second alphanumeric data item on top of the same memory location as a preceding data item. In the example code below, data item PERSON-REC is defined as a group containing another group and a numeric data item. PERSON-DATA is defined as an alphanumeric data item that renames PERSON-REC, treating the data bytes continued within it as character data.

```  01  PERSON-REC.
05  PERSON-NAME.
10  PERSON-NAME-LAST    PIC X(12).
10  PERSON-NAME-FIRST   PIC X(16).
10  PERSON-NAME-MID     PIC X.
05  PERSON-ID               PIC 9(9) PACKED-DECIMAL.

01  PERSON-DATA                 RENAMES PERSON-REC.
```

The second way to define a union type is by using the REDEFINES keyword. In the example code below, data item VERS-NUM is defined as a 2-byte binary integer containing a version number. A second data item VERS-BYTES is defined as a two-character alphanumeric variable. Since the second item is redefined over the first item, the two items share the same address in memory, and therefore share the same underlying data bytes. The first item interprets the two data bytes as a binary value, while the second item interprets the bytes as character values.

```  01  VERS-INFO.
05  VERS-NUM        PIC S9(4) COMP.
05  VERS-BYTES      PIC X(2)
REDEFINES VERS-NUM
```

### PL/I

In PL/I then original term for a union was cell,[3] which is still accepted as a synonym for union by several compilers. The union declaration is similar to the structure definition, where elements at the same level within the union declaration occupy the same storage. Elements of the union can be any data type, including structures and array.[4]:pp192–193 Here vers_num and vers_bytes occupy the same storage locations.

```  1  vers_info         union,
5 vers_num        fixed binary,
5 vers_bytes      pic '(2)A';
```

An alternative to a union declaration is the DEFINED attribute, which allows alternative declarations of storage, however the data types of the base and defined variables must match.[4]:pp.289–293

## Syntax and example

In C and C++, the syntax is:

```union <name>
{
<datatype>  <1st variable name>;
<datatype>  <2nd variable name>;
.
.
.
<datatype>  <nth variable name>;
} <union variable name>;
```

A structure can also be a member of a union, as the following example shows:

```union name1
{
struct name2
{
int     a;
float   b;
char    c;
} svar;
int     d;
} uvar;
```

This example defines a variable `uvar` as a union (tagged as `name1`), which contains two members, a structure (tagged as `name2`) named `svar` (which in turn contains three members), and an integer variable named `d`.

Unions may occur within structures and arrays, and vice versa:

```struct
{
int flags;
char *name;
int utype;
union {
int ival;
float fval;
char *sval;
} u;
} symtab[NSYM];
```

The number ival is referred to as symtab[i].u.ival and the first character of string sval by either of *symtab[i].u.sval or symtab[i].u.sval[0].

## Difference between Union and Structure

A union is a class all of whose data members are mapped to the same address within its object. The size of an object of a union is, therefore, the size of its largest data member.

In a structure, all of its data members are stored in contiguous memory locations. The size of an object of a struct is, therefore, the size of the sum of all its data members.

This gain in space efficiency, while valuable in certain circumstances, comes at a great cost of safety: the program logic must ensure that it only reads the field most recently written along all possible execution paths. The exception is when unions are used for type conversion: in this case, a certain field is written and the subsequently read field is deliberately different.

As an example illustrating this point, the declaration

```struct foo { int a; float b; }
```

defines a data object with two members occupying consecutive memory locations:

```                ┌─────┬─────┐
foo  │  a  │  b  │
└─────┴─────┘
↑     ↑
Memory address:  0150  0154
```

In contrast, the declaration

```union bar { int a; float b; }
```

defines a data object with two members occupying the same memory location:

```                ┌─────┐
bar  │  a  │
│  b  │
└─────┘
↑
Memory address:  0150
```

Structures are used where an "object" is composed of other objects, like a point object consisting of two integers, those being the x and y coordinates:

```typedef struct {
int x;           // x and y are separate
int y;
} tPoint;
```

Unions are typically used in situation where an object can be one of many things but only one at a time, such as a type-less storage system:

```typedef enum { STR, INT } tType;
typedef struct {
tType typ;          // typ is separate.
union {
int ival;       // ival and sval occupy same memory.
char *sval;
};
} tVal;
```

## References

1. ^ Ritchie, Dennis M. (March 1993). "The Development of the C Language". ACM SIGPLAN Notices. 28 (3): 201–208. doi:10.1145/155360.155580. The scheme of type composition adopted by C owes considerable debt to Algol 68, although it did not, perhaps, emerge in a form that Algol's adherents would approve of. The central notion I captured from Algol was a type structure based on atomic types (including structures), composed into arrays, pointers (references), and functions (procedures). Algol 68's concept of unions and casts also had an influence that appeared later.
2. ^ "6.63 Unnamed Structure and Union Fields". Retrieved 2016-12-29.
3. ^ IBM Corporation (March 1968). IBM System/360 PL/I Language Specifications (PDF). p. 52. Retrieved Jan 22, 2018.
4. ^ a b IBM Corporation (Dec 2017). Enterprise PL/I for z/OS PL/I for AIX IBM Developer for z Systems PL/I for windows Language Reference (PDF). Retrieved Jan 22, 2018.