With the code:
#include
class A {};
class B { char x; };
int main()
{
std::cerr << sizeof(A) << \" \" << sizeof(B) &
This isn’t really a meaningful question: The runtime just marks the one byte as occupied so that no other object will be allocated at its position. But there isn’t anything “held” there to occupy the byte.
The only reason for this rule is that objects must be uniquely identifiable. An object is identified by the address it has in memory. To ensure that no two objects have the same address (except in the case of base class objects), objects of empty classes “occupy” memory by having a non-zero size.
There is no requirement in the C++ standard that an empty object should have one byte of memory occupied. It is purely based on the implementation.
EDIT: true, it's conforming ( ISO/IEC 14882 p.149 ):
9 Classes [class]
..
..
..
3 Complete objects and member subobjects of class type shall have nonzero size ...
You can often see a similar effect in classes like these :
class Foo {
int a;
char b;
}; // sizeof(Foo) > sizeof(int) + sizeof(char)
Not all memory in a C++ object needs to have a name. Unnames memory inside an object is commnoly called "padding". Your empty class happens to have one byte of padding. One of the most common reasons why C++ compilers insert padding is to allow use of a class in an array type.