Virtual constructor & virtual copy constructor

virtual constructor :  virtual constructor is function that creates different type of object of objects depending on the input it is given.

Example: Factory design pattern is the example of virtual constructor.

virtual copy constructor : virtual copy constructor returns a pointer to a new copy of the the object invoking the function. Because of this behaviour, virtual copy constructor is also known as 'copyself', 'cloneself' or just 'clone'.

class base {
    public:
        virtual base* clone() = 0;
};

class Text : public base
{
    public:
        virtual Text* clone()
        {
            return new Text(*this);
        }
};

class Image : public base
{
    public:
        virtual Image* clone()
        {
            return new Image(*this);
        }
};

If real copy constructor perform swallow copy, then virtual copy constructor also perform swallow copy. If real copy constructor perform deep copy then virtual copy constructor perform deep copy.

Comments

Post a Comment

Popular posts from this blog

IPC (Inter-Process Communication) on Linux

IPC 1.  Pipes 2.  Named pipes (also called as FIFO) 3.  Signals 4.  Message queue 5.  Shared memory 6.  Semaphores 7.  Sockets 1. Pipes:     Types:             a. Anonymous pipes             b. Named pipes OR FIFO     a. Anonymous pipes:         - Created b/w related processes         - Generally, parent ancestor create pipe and the fork child process. Each child process get access             to pipe.         - one end of pipe is read only and other is write only. This means pipe is half duplex.         - generally used to send data stream from one process to another (like | command in Linux)         - pipe is automatically deleted at the end of proccess         - Once data is read, cant be read aga...
Read more

Difference between new and malloc

new/delete Allocate/release memory Memory allocated from 'Free Store' Returns a fully typed pointer. new (standard version) never returns a NULL (will throw on failure) Are called with Type-ID (compiler calculates the size) Has a version explicitly to handle arrays. Reallocating (to get more space) not handled intuitively (because of copy constructor). Whether they call malloc/free is implementation defined. Can add a new memory allocator to deal with low memory (set_new_handler) operator new/delete can be overridden legally constructor/destructor used to initialize/destroy the object malloc/free Allocates/release memory Memory allocated from 'Heap' Returns a void* Returns NULL on failure Must specify the size required in bytes. Allocating array requires manual calculation of space. Reallocating larger chunk of memory simple (No copy constructor to worry about) They will  NOT  call new/delete No way to splice user code into the allocation se...
Read more

Vitrual Function Implementation

To implement virtual functions, C++ uses a special form of late binding known as the virtual table. The virtual table is a lookup table of functions used to resolve function calls in a dynamic/late binding manner. The virtual table sometimes goes by other names, such as “vtable”, “virtual function table”, “virtual method table”, or “dispatch table”. Because knowing how the virtual table works is not necessary to use virtual functions, this section can be considered optional reading. The virtual table is actually quite simple, though it’s a little complex to describe in words. First, every class that uses virtual functions (or is derived from a class that uses virtual functions) is given its own virtual table. This table is simply a static array that the compiler sets up at compile time. A virtual table contains one entry for each virtual function that can be called by objects of the class. Each entry in this table is simply a function pointer that points to the most-derived functi...
Read more