Webinar: Evaluation - 05.12
An incomplete type tells the compiler that a type with this name exists but it does not tell anything about how a type is implemented. For example, it doesn't tell what functions, variables are there. Usually, these types are fully defined later, so this declaration is often called a forward declaration.
Incomplete types include:
For the type to become complete (fully defined), we must specify the missing information. It is also worth noting the void type, which cannot be complete at all.
An incomplete type does not tell the compiler anything about its internal structure. Thus, we cannot compile code that tries to access its contents. It is also impossible to perform operations that require knowledge of the exact type size. To do this, we need to know the size of the types that are contained in the required class.
We can obtain an incomplete type by using the following language constructs:
Forward - declaration:
class MyType;
Pointer to an unknown type:
struct MyType *myPtr;
An array containing elements of an incomplete type (even if the number of elements is known):
MyType b[10];
In all these cases, for a complete definition of the type, we are obliged to provide an implementation of the 'MyType' type somewhere. For example, this:
class MyType {
int someNumber;
}
In this case, all restrictions imposed on incomplete types will be removed.
The situation with arrays of indeterminate size deserves a separate explanation since there are several nuances when using them. For example:
extern int a[]; // Incomplete type (an array of unknown
// size with the elements of the 'int' type)
int b[] = { 1, 2, 3 }; // Complete type
// (an array of three values of the 'int' type)
int c[10]; // Complete type
Also, references and pointers can be created to arrays of unknown size, but in C++ they cannot be initialized (or assigned) by pointers to arrays with a known size. This restriction is absent in the C language because pointers to ordinary arrays and to arrays of unknown size are compatible there, and therefore can be freely converted and assigned in both directions.
extern int a[];
int (&a1)[] = a; // OK
int (*a2)[] = &a; // OK
int (*a3)[2] = &a; // Error in C++, but correct in C
int b[] = {1, 2, 3};
int (&b1)[] = b; // Error
int (*b2)[] = &b; // Error in C++, but correct in C
0