Book Image

Introduction to JVM Languages

Book Image

Introduction to JVM Languages

Overview of this book

Anyone who knows software development knows about the Java Virtual Machine. The Java Virtual Machine is responsible for interpreting Java byte code and translating it into actions. In the beginning, Java was the only programming language used for the JVM. But increasing complexity of the language and the remarkable performance of the JVM created an opening for a new generation of programming languages. If you want to build a strong foundation with the Java Virtual Machine and get started with popular modern programming languages, then this book is for you. The book will begin with a general introduction of the JVM and its features, which are common to the JVM languages, helping you get abreast with its concepts. It will then dive into explaining languages such as Java, Scala, Clojure, Kotlin, and Groovy and will show how to work with each language, their features, use cases, and pros and cons. By writing example projects in those languages and focusing on each language’s strong points, it will help you find the programming language that is most appropriate for your particular needs. By the end of the book, you will have written multiple programs that run on the Java Virtual Machine and know about the differences between the various languages.
Table of Contents (21 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Style guide


No official up-to-date Java language style guide is available from Oracle until now. The closest to this is a document from 1999 by Sun Microsystems, which is still archived on the Java website at the time of writing this. Some of its most important points, which are still relevant today, are:

  • It is recommended that you start each file of a project with the same header comments that at least contain the class name and copyright information.
  • The public class, or public interface, must be the first entry in the file. If the file has other classes or interfaces with other access modifiers, they need to be added below the public class or interface.
  • This is the order we follow when defining a class or interface:
    1. Javadoc headers of the class or interface (this topic will be discussed in the next chapter).
    2. The class or interface keyword (including the access modifiers and other modifiers). After the class or interface name, the { character that starts the class block should be on the same...