Speaking of Java 8, lambda (closure) and virtual extension method (default method) will first come to mind. This feature has already been hyped by major technology websites, and it is also the first thing we will talk about at the beginning of our Java 8 series. Features (JEP126 http://openjdk.java.net/jeps/126), some libraries of jdk8 have been redesigned using lambda expressions. Understanding it is of great significance to learning the new features of Java 8.
1. Functional interface
Functional interface (functional interface is also called functional interface, but it is actually the same thing). Simply put, a functional interface is an interface that contains only one method. For example, java.lang.Runnable and java.util.Comparator in the Java standard library are typical functional interfaces. Java 8 provides @FunctionalInterface as an annotation. This annotation is not necessary. As long as the interface meets the standards of functional interfaces (that is, an interface that only contains one method), the virtual machine will automatically determine it. However, it is best to use the annotation @FunctionalInterface on the interface to declare it. This prevents other members of the team from mistakenly adding new methods to the interface.
Lambda in Java cannot appear alone. It requires a functional interface to flourish. The lambda expression method body is actually the implementation of the functional interface. The grammar will be discussed below.
2. Lambda syntax
Contains three parts
1. A formal parameter separated by commas in parentheses. The parameter is the parameter of the method in the functional interface
2. An arrow symbol:- >
3. The method body can be an expression or a code block. The method body is the implementation of the method in the functional interface. If it is a code block, it must be wrapped with {} and a return is required. value, but there is an exception. If the return value of the method in the functional interface is void, there is no need to {}
The overall look is like this:
(parameters) -> expression 或者 (parameters) -> { statements; }
Look at a complete example for easy understanding
/** * 测试lambda表达式 * * @author benhail */ public class TestLambda { public static void runThreadUseLambda() { //Runnable是一个函数接口,只包含了有个无参数的,返回void的run方法; //所以lambda表达式左边没有参数,右边也没有return,只是单纯的打印一句话 new Thread(() ->System.out.println("lambda实现的线程")).start(); } public static void runThreadUseInnerClass() { //这种方式就不多讲了,以前旧版本比较常见的做法 new Thread(new Runnable() { @Override public void run() { System.out.println("内部类实现的线程"); } }).start(); } public static void main(String[] args) { TestLambda.runThreadUseLambda(); TestLambda.runThreadUseInnerClass(); } }
It can be seen that the code designed using lambda expressions will be more concise and readable.
3. Method reference
is actually a simplified way of writing lambda expression. The referenced method is actually the method body implementation of lambda expression. The syntax is also very simple. On the left is the container (can is the class name, instance name), in the middle is "::", and on the right is the corresponding method name. As shown below:
ObjectReference::methodName
The reference format of a general method is
If it is a static method, it is ClassName::methodName. For example, Object::equals
If it is an instance method, it is Instance::methodName. For example, Object obj=new Object();obj::equals;
constructor. Then it is ClassName::new
Let’s look at a complete example for easy understanding:
import java.awt.FlowLayout; import java.awt.event.ActionEvent; import javax.swing.JButton; import javax.swing.JFrame; /** * * @author benhail */ public class TestMethodReference { public static void main(String[] args) { JFrame frame = new JFrame(); frame.setLayout(new FlowLayout()); frame.setVisible(true); JButton button1 = new JButton("点我!"); JButton button2 = new JButton("也点我!"); frame.getContentPane().add(button1); frame.getContentPane().add(button2); //这里addActionListener方法的参数是ActionListener,是一个函数式接口 //使用lambda表达式方式 button1.addActionListener(e -> { System.out.println("这里是Lambda实现方式"); }); //使用方法引用方式 button2.addActionListener(TestMethodReference::doSomething); } /** * 这里是函数式接口ActionListener的实现方法 * @param e */ public static void doSomething(ActionEvent e) { System.out.println("这里是方法引用实现方式"); } }
It can be seen that the doSomething method is the implementation of lambda expression. The advantage of this is that if you feel that the lambda method is very long and affects the readability of the code, method reference is a solution
IV. Summary
The above is the entire content of lambda expression syntax. I believe everyone has a certain understanding of lambda expressions. However, if the code is simple, it will not impress many viewers, and neither does Java 8. It is so exciting. In fact, the urgent need for the introduction of lambda in Java 8 is because lambda expressions can simplify multi-thread or multi-core processing of data on collections and provide faster collection processing speed. This will be discussed later on JEP126. Features will be divided into 3 parts. The reason why they are separated is because there are too many things that can be written about this feature. This part makes readers familiar with the syntax and concepts of lambda expressions and method references. The second part is virtual extension methods (default method), the last part is about the processing of large data collections, unraveling the mystery of the most powerful effect of lambda expressions.
For more articles related to the analysis of Lambda expressions, the new features of Java 8, please pay attention to the PHP Chinese website!

Emerging technologies pose both threats and enhancements to Java's platform independence. 1) Cloud computing and containerization technologies such as Docker enhance Java's platform independence, but need to be optimized to adapt to different cloud environments. 2) WebAssembly compiles Java code through GraalVM, extending its platform independence, but it needs to compete with other languages for performance.

Different JVM implementations can provide platform independence, but their performance is slightly different. 1. OracleHotSpot and OpenJDKJVM perform similarly in platform independence, but OpenJDK may require additional configuration. 2. IBMJ9JVM performs optimization on specific operating systems. 3. GraalVM supports multiple languages and requires additional configuration. 4. AzulZingJVM requires specific platform adjustments.

Platform independence reduces development costs and shortens development time by running the same set of code on multiple operating systems. Specifically, it is manifested as: 1. Reduce development time, only one set of code is required; 2. Reduce maintenance costs and unify the testing process; 3. Quick iteration and team collaboration to simplify the deployment process.

Java'splatformindependencefacilitatescodereusebyallowingbytecodetorunonanyplatformwithaJVM.1)Developerscanwritecodeonceforconsistentbehavioracrossplatforms.2)Maintenanceisreducedascodedoesn'tneedrewriting.3)Librariesandframeworkscanbesharedacrossproj

To solve platform-specific problems in Java applications, you can take the following steps: 1. Use Java's System class to view system properties to understand the running environment. 2. Use the File class or java.nio.file package to process file paths. 3. Load the local library according to operating system conditions. 4. Use VisualVM or JProfiler to optimize cross-platform performance. 5. Ensure that the test environment is consistent with the production environment through Docker containerization. 6. Use GitHubActions to perform automated testing on multiple platforms. These methods help to effectively solve platform-specific problems in Java applications.

The class loader ensures the consistency and compatibility of Java programs on different platforms through unified class file format, dynamic loading, parent delegation model and platform-independent bytecode, and achieves platform independence.

The code generated by the Java compiler is platform-independent, but the code that is ultimately executed is platform-specific. 1. Java source code is compiled into platform-independent bytecode. 2. The JVM converts bytecode into machine code for a specific platform, ensuring cross-platform operation but performance may be different.

Multithreading is important in modern programming because it can improve program responsiveness and resource utilization and handle complex concurrent tasks. JVM ensures the consistency and efficiency of multithreads on different operating systems through thread mapping, scheduling mechanism and synchronization lock mechanism.


Hot AI Tools

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

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

Undress AI Tool
Undress images for free

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

Atom editor mac version download
The most popular open source editor

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

Zend Studio 13.0.1
Powerful PHP integrated development environment

WebStorm Mac version
Useful JavaScript development tools
