Summary of "كورس C# OOP منحة ITI شرح م احمد ممدوح #4"

Summary of the Video: “كورس C# OOP منحة ITI شرح م احمد ممدوح #4”

This video is part of a C# Object-Oriented Programming (OOP) course taught by Engineer Ahmed Mamdouh. It focuses on deepening the understanding of OOP concepts in C#, particularly related to memory management, data types, and object creation.

Introduction to Object-Oriented Programming (OOP) concepts: Abstraction, Classes, Objects.
The course continues from the previous session, moving deeper into how objects are created and managed in memory.

Any application consists of code instructions and data.
For execution, an application must be loaded into RAM from storage.
The code (instructions) and data are loaded into two distinct areas in memory.

Used for dynamic allocation of memory.
Stores objects or data that need to persist beyond the scope of a single function.
Data remains in the heap until explicitly released or garbage collected.
Example: Objects created with the new keyword in C#.

All data types in C# fall into two categories:

Variables hold a reference (address) to the object in the heap.
The actual object contains the data and resides in the heap.
Example: csharp Car c; // declares a reference variable c but does NOT create an object c = new Car(); // allocates the object on the heap and assigns its address to c
Understanding this difference is crucial for managing and accessing data in memory.

Declaring a reference variable alone does not create an object.
The new keyword is necessary to allocate memory on the heap and create the object.
The reference variable stores the address of the object.
Accessing members of the object is done through the reference (e.g., c.Price).
Changing the reference variable to point to a new object leaves the old object unreferenced, which may later be garbage collected.

Local variables must be initialized before use.
Uninitialized variables cause compile-time errors.
Reference variables can be initialized to null to indicate they do not currently reference any object.
Attempting to access members via a null reference causes a runtime NullReferenceException.
Value types cannot be assigned null unless they are nullable types (not covered in detail here).

When an object is created, its members are automatically initialized to default values:
- Value types (e.g., int, bool) get their default values (0, false, etc.).
- Reference types get null by default.
This automatic initialization prevents uninitialized member errors.

Memory Management in C#:
- Understand the difference between stack and heap.
- Know what types of data go to stack vs heap.
- Recognize the lifetime of data in stack vs heap.
Working with Value and Reference Types:
- Value types store data directly.
- Reference types store addresses pointing to objects on the heap.
- Use the new keyword to create objects on the heap.
- Always initialize local variables before use.
Object Creation and Usage:
- Declaration of a reference variable does not create an object.
- Use new to allocate and initialize objects.
- Manage references carefully to avoid null reference errors and memory leaks.