Skip to main content

Short notes on 1. Early vs late binding 2. POP vs OOP 3. Namespaces

1. Early vs late binding

Early binding and late binding are concepts in programming that determine when the code is linked to the actual functions or methods it refers to.

Early binding is also known as static binding or compile-time binding. In early binding, the compiler knows the type of the object being referred to, and the specific function or method to be called is determined at compile-time. This means that the code is linked to the function or method before the program is executed, making it faster and more efficient.

Late binding is also known as dynamic binding or runtime binding. In late binding, the type of the object being referred to is not determined until runtime, and the specific function or method to be called is determined at runtime. This means that the code is linked to the function or method during runtime, making it slower and less efficient.

2. POP vs OOP

POP (Procedural Oriented Programming) and OOP (Object Oriented Programming) are two different programming paradigms.

The main differences between POP and OOP are as follows:

  1. Data and functions: In POP, data and functions are treated separately, and functions manipulate the data passed to them. In OOP, data and functions are encapsulated in objects.
  2. Focus: In POP, the main focus is on functions or procedures and how they are executed. In OOP, the main focus is on objects and their interactions.
  3. Reusability: In POP, functions can be reused across different programs. In OOP, objects and classes can be reused across different programs.
  4. Polymorphism: Polymorphism is easier to achieve in OOP, where objects can be used interchangeably with objects of other classes. In POP, achieving polymorphism requires more work and is less flexible
3. Namespaces

Namespaces are a feature in C++ that allow us to group related functions, classes, and variables under a single name. This helps in preventing naming conflicts and organizing code. We can create a namespace using the keyword "namespace" followed by the namespace name and enclosing the contents within curly braces. We can access the contents of a namespace using the scope resolution operator "::". For example:

namespace myNamespace {
   int myFunction() {
      // function code
   }
}
int main() {
   myNamespace::myFunction(); // accessing function from the namespace
   return 0;
}

Comments

Popular posts from this blog

Write a program using the algorithm count() to count how many elements in a container have a specified value.

 Here's an example program using the count() algorithm to count the number of occurrences of a specific value in a vector container: #include <iostream> #include <vector> #include <algorithm> using namespace std; int main() {     vector<int> numbers = { 2, 5, 3, 7, 8, 5, 1, 5, 4 };          // count the number of occurrences of the value 5 in the vector     int count = count(numbers.begin(), numbers.end(), 5);          cout << "The number of occurrences of 5 in the vector is: " << count << endl;          return 0; } Output: The number of occurrences of 5 in the vector is: 3 Explanation: The program starts by creating a vector named numbers that contains several integer values. The count() algorithm is used to count the number of occurrences of the value 5 in the numbers vector. The function takes three arguments: the beginning and end iterators of...

What are Stub and Skeleton in Distributed Application? Explain its function with block diagram.

 Stub and Skeleton are two important components of distributed applications. A distributed application is a software system that runs on multiple computers connected through a network. It allows users to access resources and services on different computers as if they were on a local computer. In a distributed application, a client program on one computer sends a request to a server program on another computer. The server program processes the request and sends a response back to the client program. Stub and Skeleton help to facilitate this communication between the client and server programs. A Stub is a client-side proxy that represents the remote object on the client machine. It acts as a gateway for the client to communicate with the server. When a client invokes a method on the Stub, it marshals the arguments and sends them to the server over the network. The Stub then waits for the server to send a response. When the response is received, the Stub unmarshals the data and retur...

Explain the lifecycle of Servlet with block diagram.

 The lifecycle of a Servlet can be divided into several stages. Here's a block diagram that illustrates the different stages: Servlet API: The Servlet API provides a standard set of interfaces and classes for creating and interacting with Servlets. It is typically included in the web application's classpath as a JAR file. Servlet Container: The Servlet Container is a web server or application server that implements the Servlet API. It provides a runtime environment for executing Servlets and manages their lifecycle. Servlet Class: The Servlet Class is the Java class that implements the javax.servlet.Servlet interface. It contains the logic for processing HTTP requests and generating HTTP responses. init(): The init() method is called once when the Servlet is first loaded by the Servlet Container. It is used for initialization tasks, such as setting up database connections, loading configuration settings, or initializing other resources that will be used by the Servlet. service(...