Skip to main content

What is the size of an Empty Class, Class with virtual functions and class with only normal functions, no data members?

Size of an Empty Class.

class MyClass {
};

MyClass myObject;
sizeof(myObject);

The size of an empty class is 1 byte.
Since size of class is calculated as the size of data members it contains.
Since empty class doesnt contains any data member, its size is zero. but to keep the existence on object in memory size of empty class object is 1 byte.

Size of Class with virtual functions

class MyClass {

public:
virtual void myfunct();
};

MyClass myObject;
sizeof(myObject);


This will be 4 bytes. as this object will contain VPTR pointer to virtual table.
As it has some size compile doesnt add one byte which it adds to the empty class.


Size of class with only normal functions, no data members?


class MyClass {

public:
void myfunct();
};

MyClass myObject;
sizeof(myObject);


This will again 1 byte as it has no data members.
Class size is comprised of only data members and not member functions.
Labels:

Comments

Anonymous said…
good explaination !

http://www.itucu.com/2010/09/what-is-the-size-of-an-object-of-a-empty-c-class/
September 8, 2010 at 10:30 AM
Post a Comment

Popular posts from this blog

Explain Polymorphism and Flavors of Polymorphism...

Polymorphism is the ability of different objects to react in an individual manner to the same message. This notion was imported from natural languages. For example, the verb "to close" means different things when applied to different objects. Closing a door, closing a bank account, or closing a program's window are all different actions; their exact meaning is determined by the object on which the action is performed. Most object-oriented languages implement polymorphism only in the form of virtual functions. But C++ has two more mechanisms of static (meaning: compile-time) polymorphism: Operator overloading. Applying the += operator to integers or string objects, for example, is interpreted by each of these objects in an individual manner. Obviously, the underlying implementation of += differs in every type. Yet, intuitively, we can predict what results are. Templates. A vector of integers, for example, reacts differently from a vector of string objects when it receives ...
17 comments
Read more

Function name mangling for C++ and Java

G++ internals - Mangling Both C++ and Jave provide overloaded function and methods, which are methods with the same types but different parameter lists. Selecting the correct version is done at compile time. Though the overloaded functions have the same name in the source code, they need to be translated into different assembler-level names, since typical assemblers and linkers cannot handle overloading. This process of encoding the parameter types with the method name into a unique name is called name mangling . The inverse process is called demangling . It is convenient that C++ and Java use compatible mangling schemes, since the makes life easier for tools such as gdb, and it eases integration between C++ and Java. Note there is also a standard "Jave Native Interface" (JNI) which implements a different calling convention, and uses a different mangling scheme. The JNI is a rather abstract ABI so Java can call methods written in C or C++; we are concerned he...
5 comments
Read more