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

Managing states with agents


To safely manage a mutable state in a multithreaded program, Clojure offers agents. Each agent is responsible for managing one object that contains its state. Most often, a state object will be stored in one of Clojure's own immutable data structures. To change the state of a particular agent, an action can be sent to it. Actions are ordinary, non-blocking functions that are executed by the agent. The return value of the action will replace the current state of the agent.

Agents run in a thread provided by an internal thread pool that is managed by Clojure. They are built to be responsive; Clojure will never place locks while handling actions. The agent's state can safely be read at any time by other code, no matter on which thread it is running. An action is sent to the agent asynchronously and is picked up later by the agent's thread. The agent's thread will execute the action and its result value will become the agent's new state.

It is possible to add a validator...