1. Abstract class
We know that objects are generated through classes, but not all classes can describe specific objects.
If a class does not contain enough information to describe a specific object, it becomes an abstract class. An abstract class is an abstraction of a class of objects that have the same characteristics but different performance details. For example, birds all call, but different birds call in different ways. The concept of "call" can be abstracted.
? Define the following bird:
public abstract class Bird { private String color; public String getColor() { return color; } public void setColor(String color) { this.color = color; } public Bird(){ } public abstract void sing();//鳴叫 } //喜鵲 class Magpie extends Bird{ public void sing() { System.out.println("I can sing in a whisper. "); } }
Abstract class characteristics:
(1) The abstract class is modified with the abstract keyword
(2) The abstract method in the abstract class is modified with the abstract keyword, and there is no method body (specific implementation ).
(3) Abstract classes can contain non-abstract methods
(4) Abstract classes do not need to contain abstract methods (there is no point in designing them as abstract classes...), but classes that contain abstract methods must be abstract classes
(5) Abstract classes are essentially classes and can only be inherited
(6) Abstract classes cannot be instantiated or new. We said before that it does not describe specific objects, and it certainly cannot be instantiated. (7) Abstract classes can have instance variables and construction methods. The contract stipulates what you can do. The software design process relies on abstraction rather than concrete implementation.
Like the USB interface on our computers, whether you have a hard drive, a USB flash drive, or a mobile phone, as long as you implement the interface specified by USB, you can connect to the computer.
In the above abstract class example, I want to add a "fly" function. Considering that not all birds can fly, such as penguins, ostriches, ducks, etc., what should I do?
It is definitely inappropriate to modify abstract classes: 1. It violates the opening and closing principle, 2: It will cause all subclasses to inherit the "flying" function, and we will see ducks flying all over the sky ^_^ .
We can define the following interface:
public interface IFly { void fly(); }
// Magpie can implement the interface in IBird:
class Magpie extends Bird implements IFly { public void sing() { System.out.println("I can sing in a whisper. "); } public void fly(){ System.out.println("我會飛了!"); } }
Magpie has implemented the fly interface in IFly and can finally fly.
So what if we need to add a swimming function to the birds? Think for yourself. . .
Characteristics of interface:
(1) Modifiers: public, abstract, default (don’t write)
(2) Keywords: interface
(3) The methods in the interface are abstract methods and cannot be implemented .
(4) The methods in the interface are public abstract by default, and the implementation class must use public modification.
(5) All methods in the interface must be implemented in the implementation class (except abstract classes).
(6) Variables in the interface are public static final by default.
(7) A class can implement multiple interfaces.
3. Application scenarios
1) Abstract classes reflect the "is a" relationship. If the implementations of certain classes have something in common, you can abstract an abstract class and let the abstract class implement common code. , and the personalized methods are implemented by each subclass.
2) The interface reflects the "like a" relationship and represents the abstract behavior of objects of different types. For example, airplanes and birds can fly, and the interface for flying can be detached, but they are not the same kind.
3) In software design, when you need to separate the interface from the implementation and encapsulate changes, interface-oriented programming is particularly important.
For example, in IOC thinking, the client does not care what class you are, the specific object is injected by the container.
Another example is the interaction between two systems. A good design is that both parties provide interfaces and do not care about the internal implementation. This reduces coupling while encapsulating changes.
Many design principles, design ideas and design patterns reflect the importance of interface-oriented programming: opening and closing principle, interface isolation, dependency inversion, adapter pattern, etc.

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

There are three common methods to traverse Map in Java: 1. Use entrySet to obtain keys and values at the same time, which is suitable for most scenarios; 2. Use keySet or values to traverse keys or values respectively; 3. Use Java8's forEach to simplify the code structure. entrySet returns a Set set containing all key-value pairs, and each loop gets the Map.Entry object, suitable for frequent access to keys and values; if only keys or values are required, you can call keySet() or values() respectively, or you can get the value through map.get(key) when traversing the keys; Java 8 can use forEach((key,value)->

Optional can clearly express intentions and reduce code noise for null judgments. 1. Optional.ofNullable is a common way to deal with null objects. For example, when taking values ??from maps, orElse can be used to provide default values, so that the logic is clearer and concise; 2. Use chain calls maps to achieve nested values ??to safely avoid NPE, and automatically terminate if any link is null and return the default value; 3. Filter can be used for conditional filtering, and subsequent operations will continue to be performed only if the conditions are met, otherwise it will jump directly to orElse, which is suitable for lightweight business judgment; 4. It is not recommended to overuse Optional, such as basic types or simple logic, which will increase complexity, and some scenarios will directly return to nu.

In Java, Comparable is used to define default sorting rules internally, and Comparator is used to define multiple sorting logic externally. 1.Comparable is an interface implemented by the class itself. It defines the natural order by rewriting the compareTo() method. It is suitable for classes with fixed and most commonly used sorting methods, such as String or Integer. 2. Comparator is an externally defined functional interface, implemented through the compare() method, suitable for situations where multiple sorting methods are required for the same class, the class source code cannot be modified, or the sorting logic is often changed. The difference between the two is that Comparable can only define a sorting logic and needs to modify the class itself, while Compar

The core workaround for encountering java.io.NotSerializableException is to ensure that all classes that need to be serialized implement the Serializable interface and check the serialization support of nested objects. 1. Add implementsSerializable to the main class; 2. Ensure that the corresponding classes of custom fields in the class also implement Serializable; 3. Use transient to mark fields that do not need to be serialized; 4. Check the non-serialized types in collections or nested objects; 5. Check which class does not implement the interface; 6. Consider replacement design for classes that cannot be modified, such as saving key data or using serializable intermediate structures; 7. Consider modifying

To deal with character encoding problems in Java, the key is to clearly specify the encoding used at each step. 1. Always specify encoding when reading and writing text, use InputStreamReader and OutputStreamWriter and pass in an explicit character set to avoid relying on system default encoding. 2. Make sure both ends are consistent when processing strings on the network boundary, set the correct Content-Type header and explicitly specify the encoding with the library. 3. Use String.getBytes() and newString(byte[]) with caution, and always manually specify StandardCharsets.UTF_8 to avoid data corruption caused by platform differences. In short, by

Method reference is a way to simplify the writing of Lambda expressions in Java, making the code more concise. It is not a new syntax, but a shortcut to Lambda expressions introduced by Java 8, suitable for the context of functional interfaces. The core is to use existing methods directly as implementations of functional interfaces. For example, System.out::println is equivalent to s->System.out.println(s). There are four main forms of method reference: 1. Static method reference (ClassName::staticMethodName); 2. Instance method reference (binding to a specific object, instance::methodName); 3.

JavaScript data types are divided into primitive types and reference types. Primitive types include string, number, boolean, null, undefined, and symbol. The values are immutable and copies are copied when assigning values, so they do not affect each other; reference types such as objects, arrays and functions store memory addresses, and variables pointing to the same object will affect each other. Typeof and instanceof can be used to determine types, but pay attention to the historical issues of typeofnull. Understanding these two types of differences can help write more stable and reliable code.

There are three common ways to parse JSON in Java: use Jackson, Gson, or org.json. 1. Jackson is suitable for most projects, with good performance and comprehensive functions, and supports conversion and annotation mapping between objects and JSON strings; 2. Gson is more suitable for Android projects or lightweight needs, and is simple to use but slightly inferior in handling complex structures and high-performance scenarios; 3.org.json is suitable for simple tasks or small scripts, and is not recommended for large projects because of its lack of flexibility and type safety. The choice should be decided based on actual needs.
