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

Quiz


  1. Can Scala be considered a pure OOP and functional programming language?

a) Yes, Scala is both a pure OOP and functional programming language

b) No, Scala is a pure OOP language, but it cannot be considered a pure functional programming language

c) No, Scala is a pure functional programming language, but it cannot be considered a pure OOP language

d) No, Scala is neither pure OOP, nor a pure functional programming language

 

  1. Will this code compile? If not, why?
        class A { def method1 = {} }
        trait B { def method2 }
        trait C { def method3 }
        abstract class D extends A with B with C { }

a) Yes, it will compile and run correctly

b) No, traits need to be implemented using the implements keyword

c) No, class D does not implement the methods from class A and/or trait B and trait C

d) Answers b and c are correct

  1. What's wrong with the following class definition?
        public class A

a) This class will compile fine; nothing is wrong

b) It will not compile because no body (= { ...