Understanding Abstraction in Kotlin OOP

Hello, fellow coder! Today, we'll dive into Kotlin's Abstraction principle, a powerful tool in Object-Oriented Programming. Abstraction is our superhero against seemingly overwhelming complexity, revealing only the necessary details. Are you ready for the fun?

Imagine abstraction as a superboat, stripping off the complexities and giving you just the essentials to operate effectively. It’s not about understanding all the intricate details; it is about focusing on what truly matters. Think of it this way — to drive a car, you only engage with its external controls while the complex workings beneath remain hidden.

In Kotlin, objects are defined through classes. Every class serves as a preliminary blueprint for an object. It stipulates both the data (properties) and their potential behaviors (functions). Similar to a car’s control panel, an object's class provides a user-friendly interface, concealing the complex mechanics within.

When utilizing a Kotlin List, you employ functions like add(), remove(), and sort() through the appropriate collections. You do so without needing to comprehend how Kotlin manages the list's memory space. The internal workings are abstracted.

In Kotlin, classes that possess abstract functions are termed abstract classes. An abstract class is like the pearl inside an oyster, housing at least one abstract function. Each abstract function in an abstract class awaits its implementation in subclasses.

Consider this simple example:

abstract class AbstractClassExample {
    // This function is waiting to be overridden
    abstract fun doSomething()
}

fun main() {
    // val instance = AbstractClassExample() // Will cause a compile-time error
}

As you can see, you cannot instantiate an abstract class, as it's just a skeleton for the future class that will be derived from it. The abstract keyword marks a function as abstract, meaning that's a property/behavior that this class supports, but it has not been implemented yet.

For instance, when crafting a doodling app that handles shapes, you would define an abstract base class called Shape. It would have area and perimeter as its abstract functions:

abstract class Shape {
    abstract fun area(): Double
    abstract fun perimeter(): Double
}

To create actual shapes like Rectangle and Circle, you would inherit traits from Shape and define area and perimeter.

class Rectangle(private val width: Double, private val height: Double) : Shape() {
    override fun area(): Double {
        return width * height
    }

    override fun perimeter(): Double {
        return 2 * (width + height)
    }
}

class Circle(private val radius: Double) : Shape() {
    override fun area(): Double {
        return Math.PI * radius * radius
    }

    override fun perimeter(): Double {
        return 2 * Math.PI * radius
    }
}

fun main() {
    val rectangle: Shape = Rectangle(2.0, 3.0) // A rectangle with sides 2 and 3
    println("Rectangle area: ${rectangle.area()}") // Prints: Rectangle area: 6.0
    println("Rectangle perimeter: ${rectangle.perimeter()}") // Prints: Rectangle perimeter: 10.0

    val circle: Shape = Circle(5.0) // A circle with a radius of 5
    println("Circle area: ${circle.area()}") // Prints: Circle area: 78.5
    println("Circle perimeter: ${circle.perimeter()}") // Prints: Circle perimeter: 31.4
}

Shape classes provide an abstraction layer, reducing the knowledge you require to calculate the area and perimeter.