Explain the meaning and application of the Liskov Substitution Principle in object-oriented programming.

The Liskov Substitution Principle (LSP) is one of the five SOLID principles in object-oriented programming. It states that objects of a subclass should be interchangeable with objects of the superclass without affecting the correctness of the program.

This means that if class B inherits from class A, then anywhere an object of type A is expected, an object of type B can be used, and the program's behavior will remain correct.

Applying LSP helps create class hierarchies where subclasses extend the functionality of the base class without changing its expected behavior. This improves maintainability, extensibility, and reliability of the code.

Example of violating LSP:

class Bird {
    public virtual void Fly() { /* implementation of flying */ }
}

class Ostrich : Bird {
    public override void Fly() {
        throw new NotSupportedException("Ostriches do not fly");
    }
}

Here, Ostrich inherits from Bird but cannot correctly implement the Fly method, which violates LSP.

A correct approach is to reconsider the hierarchy or split interfaces so that subclasses are not forced to implement unsupported operations.