Hello everyone! Today, in today's lesson, we will talk about a very interesting topic in object-oriented programming. That's the difference between Interface and Abstract Class. When should we use Interface? When is Abstract Class the right choice? And let's learn a few small illustrative examples of them! Let's find out together!
These are two quite "abstract" concepts, but if you understand them clearly, you will easily apply them to software design. Now let's begin!
Because this lesson is mainly a review to consolidate your knowledge before entering UML, I will try to most succinctly present the main knowledge of this section to help you understand. easy to remember and apply.
1. Definition
Interface
Interface in Java is like a "contract" that classes must implement. It only contains abstract methods and constants. When implementing this "contract", the implementing objects are required to implement the prescribed methods. From Java 8 onwards, Interface has been "upgraded" with the addition of default methods and static methods. It's so convenient, isn't it?
Abstract Class
Abstract Class is a little different. It is like a "blueprint" but can provide both concrete details (regular methods) and abstractions (abstract methods). This "blueprint" specifies the common properties or methods of the objects that inherit it, the special point is that you cannot directly instantiate an Abstract Class.
2. Key differences
Let's compare to see more clearly:
??c ?i?m | Interface | Abstract Class |
---|---|---|
T? khóa(chǎn) s? d?ng | interface | abstract class |
K? th?a | M?t l?p có th? tri?n khai nhi?u interface | M?t l?p ch? có th? k? th?a m?t abstract class |
Ph??ng th?c | Ch? ch?a ph??ng th?c tr?u t??ng (tr??c Java 8) | Có c? ph??ng th?c tr?u t??ng và th?ng th??ng |
Constructor | Kh?ng có | Có |
Bi?n | Ch? ch?a h?ng s? (public static final) | Có th? ch?a bi?n v?i m?i m?c ?? truy c?p |
T?c ?? th?c thi | Nhanh h?n (???c t?i ?u hóa(chǎn) h?n) | Ch?m h?n |
Thích h?p cho | Các hành vi chung gi?a các l?p kh?ng liên quan | Các l?p có m?i quan h? k? th?a |
It's as simple as that, but depending on the situation, you will choose the most suitable one!
3. When should it be used?
Interface
You should use Interface when:
- Want to define a set of behavior that multiple (unrelated) classes can implement. For example: Fly, swim, run.
- Need to support multiple inheritance, because Java does not allow multiple inheritance with Abstract Class.
Abstract Class
Abstract Class is appropriate if:
- You want to share code between "related" (directly related) classes.
- Need to define reusable properties or methods in the subclass. For example: All animals "eat" and "sleep".
4. Illustrative example
Interface
Imagine you are building a program about animals:
public interface Animal { void eat(); void sleep(); } public class Dog implements Animal { @Override public void eat() { System.out.println("Dog eats bones"); } @Override public void sleep() { System.out.println("Dog sleeps in a kennel"); } }
As you can see, Dog only needs to implement the behavior defined in the Interface.
Abstract Class
What if animals have a few things in common but each species "eats" in its own way?
public abstract class Animal { abstract void eat(); void sleep() { System.out.println("This animal sleeps"); } } public class Dog extends Animal { @Override public void eat() { System.out.println("Dog eats bones"); } }
Here, Dog does not need to define the "sleep" behavior because it is already available from the Abstract Class!
5. Summary
So we now understand more about the difference between Interface and Abstract Class. In short:
- If you need "multiple inheritance" or unrelated classes that perform the same behavior, choose Interface.
- If you want to share code and related classes, select Abstract Class.
Thank you for following! Any questions? Don't hesitate to leave a comment! ?
The above is the detailed content of Interface và Abstract class. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The difference between HashMap and Hashtable is mainly reflected in thread safety, null value support and performance. 1. In terms of thread safety, Hashtable is thread-safe, and its methods are mostly synchronous methods, while HashMap does not perform synchronization processing, which is not thread-safe; 2. In terms of null value support, HashMap allows one null key and multiple null values, while Hashtable does not allow null keys or values, otherwise a NullPointerException will be thrown; 3. In terms of performance, HashMap is more efficient because there is no synchronization mechanism, and Hashtable has a low locking performance for each operation. It is recommended to use ConcurrentHashMap instead.

StaticmethodsininterfaceswereintroducedinJava8toallowutilityfunctionswithintheinterfaceitself.BeforeJava8,suchfunctionsrequiredseparatehelperclasses,leadingtodisorganizedcode.Now,staticmethodsprovidethreekeybenefits:1)theyenableutilitymethodsdirectly

The JIT compiler optimizes code through four methods: method inline, hot spot detection and compilation, type speculation and devirtualization, and redundant operation elimination. 1. Method inline reduces call overhead and inserts frequently called small methods directly into the call; 2. Hot spot detection and high-frequency code execution and centrally optimize it to save resources; 3. Type speculation collects runtime type information to achieve devirtualization calls, improving efficiency; 4. Redundant operations eliminate useless calculations and inspections based on operational data deletion, enhancing performance.

Instance initialization blocks are used in Java to run initialization logic when creating objects, which are executed before the constructor. It is suitable for scenarios where multiple constructors share initialization code, complex field initialization, or anonymous class initialization scenarios. Unlike static initialization blocks, it is executed every time it is instantiated, while static initialization blocks only run once when the class is loaded.

Java uses wrapper classes because basic data types cannot directly participate in object-oriented operations, and object forms are often required in actual needs; 1. Collection classes can only store objects, such as Lists use automatic boxing to store numerical values; 2. Generics do not support basic types, and packaging classes must be used as type parameters; 3. Packaging classes can represent null values ??to distinguish unset or missing data; 4. Packaging classes provide practical methods such as string conversion to facilitate data parsing and processing, so in scenarios where these characteristics are needed, packaging classes are indispensable.

Factory mode is used to encapsulate object creation logic, making the code more flexible, easy to maintain, and loosely coupled. The core answer is: by centrally managing object creation logic, hiding implementation details, and supporting the creation of multiple related objects. The specific description is as follows: the factory mode handes object creation to a special factory class or method for processing, avoiding the use of newClass() directly; it is suitable for scenarios where multiple types of related objects are created, creation logic may change, and implementation details need to be hidden; for example, in the payment processor, Stripe, PayPal and other instances are created through factories; its implementation includes the object returned by the factory class based on input parameters, and all objects realize a common interface; common variants include simple factories, factory methods and abstract factories, which are suitable for different complexities.

InJava,thefinalkeywordpreventsavariable’svaluefrombeingchangedafterassignment,butitsbehaviordiffersforprimitivesandobjectreferences.Forprimitivevariables,finalmakesthevalueconstant,asinfinalintMAX_SPEED=100;wherereassignmentcausesanerror.Forobjectref

There are two types of conversion: implicit and explicit. 1. Implicit conversion occurs automatically, such as converting int to double; 2. Explicit conversion requires manual operation, such as using (int)myDouble. A case where type conversion is required includes processing user input, mathematical operations, or passing different types of values ??between functions. Issues that need to be noted are: turning floating-point numbers into integers will truncate the fractional part, turning large types into small types may lead to data loss, and some languages ??do not allow direct conversion of specific types. A proper understanding of language conversion rules helps avoid errors.
