/explore
|
You are here 
|
blog.gradle.org | ||
| | | | |
benjiweber.co.uk
|
|
| | | | | ||
| | | | |
www.morling.dev
One of the ultimate strengths of Java is its strong notion of backwards compatibility: Java applications and libraries built many years ago oftentimes run without problems on current JVMs, and the compiler of current JDKs can produce byte code, that is executable with earlier Java versions. For instance, JDK 16 supports byte code levels going back as far as to Java 1.7; But: hic sunt dracones. The emitted byte code level is just one part of the story. It's equally important to consider which APIs of the ... |
|
| | | | | ||
| | | | |
connorberry.com
Language Comparison Perl: while (<>) { print "$. : $_" } Perl: while (<>) { print "$. : $_" } CSharp: using System; using System.IO; class App { public static void Main(string[] args) { int line_number = 1; foreach (string arg in args) { foreach (string line in File.ReadLines(arg)) { Console.WriteLine(line_number + ":" + line);... |
|
| | | | | ||
| | | | |
in.relation.to
Java 9 comes with a new feature very useful to library authors: multi-release JARs (JEP 238). A multi-release JAR (MR JAR) may contain multiple variants of one and the same class, each targeting a specific Java version. At runtime, the right variant of the class will be loaded automatically, depending on the Java version being used. This allows library authors to take advantage of new Java versions early on, while keeping compatibility with older versions at the same time. If for instance your library pe... |
|
| | | |||
