Skip to main content

Understanding Dynamic Arrays and Objects in C++

 Understanding Dynamic Arrays and Objects in C++

  • Dynamic Arrays: In C++, arrays are typically fixed-size at compile time. Dynamic arrays, also known as std::vector, provide a flexible way to create arrays whose size can be determined or modified at runtime. They automatically manage memory allocation and deallocation, reducing the risk of memory leaks.
  • Objects: Objects encapsulate data (member variables) and behavior (member functions) within a self-contained unit. In OOP, objects interact with each other through method calls, adhering to the principles of data abstraction, encapsulation, inheritance, and polymorphism.

Creating Dynamic Arrays of Objects

There are two main approaches to create dynamic arrays of objects in C++:

  1. Using std::vector:

    C++
    #include <iostream>
    #include <vector>
    
    class Point {
        int x, y;
    public:
        Point(int xVal, int yVal) : x(xVal), y(yVal) {}
        void print() const {
            std::cout << "(" << x << ", " << y << ")" << std::endl;
        }
    };
    
    int main() {
        // Create a dynamic array of 5 Point objects
        std::vector<Point> points(5);
    
        // Initialize the objects' values
        for (int i = 0; i < 5; ++i) {
            points[i] = Point(i, i + 1);
        }
    
        // Access and manipulate objects
        for (const Point& point : points) {
            point.print();
        }
    
        return 0;
    }
    

    In this example:

    • The std::vector class template is used to create a vector points that can hold Point objects.
    • The constructor std::vector<Point>(5) initializes the vector with 5 default-constructed Point objects.
    • A loop iterates over the vector, initializing each Point object with specific values using its constructor.
    • Another loop iterates over the vector, accessing and printing the objects using the print() method.
  2. Using new and delete (manual memory management):

    C++
    #include <iostream>
    
    class Shape {
    public:
        virtual void draw() const = 0;
        ~Shape() = default; // Destructor for proper memory deallocation
    };
    
    class Circle : public Shape {
        int radius;
    public:
        Circle(int radiusVal) : radius(radiusVal) {}
        void draw() const override {
            std::cout << "Drawing a circle with radius " << radius << std::endl;
        }
        ~Circle() override {
            std::cout << "Deleting Circle object" << std::endl;
        }
    };
    
    int main() {
        // Create a dynamic array of 3 Shape pointers
        Shape** shapes = new Shape*[3];
    
        // Allocate and initialize objects
        shapes[0] = new Circle(5);
        shapes[1] = new Circle(10);
        shapes[2] = new Circle(15);
    
        // Call methods on the objects
        for (int i = 0; i < 3; ++i) {
            shapes[i]->draw();
        }
    
        // Deallocate memory manually
        for (int i = 0; i < 3; ++i) {
            delete shapes[i];
        }
        delete[] shapes;
    
        return 0;
    }
    

    In this example:

    • An abstract base class Shape is defined with a virtual draw() method.
    • A derived class Circle inherits from Shape and implements the draw() method.
    • A pointer array shapes is dynamically allocated using new to hold Shape pointers.
    • Individual objects are created using new and assigned to the corresponding elements in the array.
    • The virtual draw() method is called on each object using polymorphism.
    • Memory is manually deallocated using delete for each object and then for the array itself.

Key Considerations and Best Practices

  • Prefer std::vector for most cases: std::vector offers automatic memory management, safer bounds checking, and iterator-based access

Comments

Popular posts from this blog

Installation Steps

Download the Installer: Visit the website of the application you want to install and locate the download link for the Windows version. Usually, this will be an executable file (.exe) or a compressed file (.zip) containing the installer. Run the Installer: Once the installer file is downloaded, locate it in your downloads folder or wherever you saved it. Double-click on the installer file to run it. If it's a compressed file, extract its contents first and then run the installer. User Account Control (UAC) Prompt: Windows might display a User Account Control prompt asking for permission to make changes to your device. Click "Yes" to proceed with the installation. Setup Wizard: Most installers launch a setup wizard that guides you through the installation process. Follow the on-screen instructions which may involve accepting the license agreement, choosing the installation directory, and selecting any additional options or components you want to install. Installation Pr...

Spawning Processes of Linux OS

In Linux, spawning a process refers to the act of creating a new program execution instance. This essentially means creating a new child process from an existing parent process. Spawning allows for multitasking and running multiple programs concurrently on your system. Here's a breakdown of the mechanics: The core concept: Parent process:  The existing process that initiates the spawning. Child process:  The newly created process that inherits resources like memory and open files from the parent, but has its own execution path. The tools for spawning: fork() system call:  Creates a copy of the parent process, forming the basis for the child process. exec() system call:  Replaces the current process image with a new program, essentially loading and executing the child program within the child process. The two-step approach: fork():  Creates a near-identical copy of the parent process, including memory and file descriptors. This essentially duplicates the parent p...

Private, Protected and Public Members

  In C++ Object-Oriented Programming (OOP), access specifiers control how members (data and functions) of a class can be accessed from different parts of your program. These are crucial for understanding data encapsulation and promoting secure object-oriented design. Access Specifiers: Public:  Members are accessible from anywhere in your program, including outside the class, its subclasses, and friend functions. Use them cautiously to avoid exposing internal implementation details unnecessarily. Private:  Members are accessible only within the class and its friend functions. This promotes data encapsulation and protects data integrity by restricting direct access from outside. Protected:  Members are accessible within the class, its subclasses, and their friend functions. Useful for inheritance scenarios where subclasses need controlled access to base class members. Benefits of Each: Public:  Provides direct access and ...