The Well-Grounded Java Developer

Total Page:16

File Type:pdf, Size:1020Kb

The Well-Grounded Java Developer Vital techniques of Java 7 and polyglot programming The Benjamin J. Evans Martijn Verburg FOREWORD BY Dr. Heinz Kabutz MANNING RULES OF THE JAVA MEMORY MODEL Example of Synchronizes-With JMM has the following rules: ■ An unlock operation on a monitor Synchronizes-With later lock operations ■ A write to a volatile variable Synchronizes-With later reads of the variable ■ If an action A Synchronizes-With action B, then A Happens-Before B ■ If A comes before B in program order within a thread, then A Happens-Before B Read more in chapter 4. The Well-Grounded Java Developer The Well-Grounded Java Developer VITAL TECHNIQUES OF JAVA 7 AND POLYGLOT PROGRAMMING BENJAMIN J. EVANS MARTIJN VERBURG MANNING SHELTER ISLAND For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. 20 Baldwin Road PO Box 261 Shelter Island, NY 11964 Email: [email protected] ©2013 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine. Manning Publications Co. Development editors: Renae Gregoire, Karen G. Miller 20 Baldwin Road Copyeditor: Andy Carroll PO Box 261 Proofreader: Elizabeth Martin Shelter Island, NY 11964 Typesetter: Dennis Dalinnik Cover designer: Marija Tudor ISBN: 9781617290060 Printed in the United States of America 1 2 3 4 5 6 7 8 9 10 – MAL – 18 17 16 15 14 13 12 brief contents PART 1 DEVELOPING WITH JAVA 7 .............................................1 1 ■ Introducing Java 7 3 2 ■ New I/O 20 PART 2 VITAL TECHNIQUES .....................................................51 3 ■ Dependency Injection 53 4 ■ Modern concurrency 76 5 ■ Class files and bytecode 119 6 ■ Understanding performance tuning 150 PART 3 POLYGLOT PROGRAMMING ON THE JVM....................191 7 ■ Alternative JVM languages 193 8 ■ Groovy: Java’s dynamic friend 213 9 ■ Scala: powerful and concise 241 10 ■ Clojure: safer programming 279 PART 4 CRAFTING THE POLYGLOT PROJECT ...........................311 11 ■ Test-driven development 313 12 ■ Build and continuous integration 342 13 ■ Rapid web development 380 14 ■ Staying well-grounded 410 v contents foreword xvii preface xix acknowledgments xxi about this book xxiv about the authors xxix about the cover illustration xxx PART 1 DEVELOPING WITH JAVA 7..................................1 Introducing Java 7 3 1 1.1 The language and the platform 4 1.2 Small is beautiful—Project Coin 5 1.3 The changes in Project Coin 9 Strings in switch 9 ■ Enhanced syntax for numeric literals 10 ■ Improved exception handling 12 Try-with-resources (TWR) 13 ■ Diamond syntax 16 Simplified varargs method invocation 17 1.4 Summary 19 New I/O 20 2 2.1 Java I/O—a history 22 Java 1.0 to 1.3 22 ■ Java 1.4 and NIO 23 Introducing NIO.2 24 vii viii CONTENTS 2.2 Path—a foundation of file-based I/O 24 Creating a Path 27 ■ Retrieving information from a Path 27 Removing redundancies 28 ■ Converting Paths 29 NIO.2 Path and Java’s existing File class 30 2.3 Dealing with directories and directory trees 30 Finding files in a directory 30 ■ Walking the directory tree 31 2.4 Filesystem I/O with NIO.2 33 Creating and deleting files 34 ■ Copying and moving files 35 File attributes 36 ■ Reading and writing data quickly 40 File change notification 41 ■ SeekableByteChannel 42 2.5 Asynchronous I/O operations 43 Future style 44 ■ Callback style 46 2.6 Tidying up Socket-Channel functionality 47 NetworkChannel 48 ■ MulticastChannel 49 2.7 Summary 50 PART 2 VITAL TECHNIQUES .........................................51 Dependency Injection 53 3 3.1 Inject some knowledge—understanding IoC and DI 54 Inversion of Control 54 ■ Dependency Injection 55 Transitioning to DI 56 3.2 Standardized DI in Java 61 The @Inject annotation 62 ■ The @Qualifier annotation 64 The @Named annotation 65 ■ The @Scope annotation 65 The @Singleton annotation 66 ■ The Provider<T> interface 66 3.3 Guice 3—the reference implementation for DI in Java 67 Getting started with Guice 68 ■ Sailor’s knots—the various bindings of Guice 70 ■ Scoping your injected objects with Guice 73 3.4 Summary 75 Modern concurrency 76 4 4.1 Concurrency theory—a primer 77 Explaining Java’s threading model 77 ■ Design concepts 79 How and why do the forces conflict? 80 ■ Sources of overhead 81 A transaction processor example 81 CONTENTS ix 4.2 Block-structured concurrency (pre-Java 5) 83 Synchronization and locks 83 ■ The state model for a thread 84 Fully synchronized objects 85 ■ Deadlocks 86 Why synchronized? 88 ■ The volatile keyword 89 Immutability 90 4.3 Building blocks for modern concurrent applications 91 Atomic classes—java.util.concurrent.atomic 92 Locks—java.util.concurrent.locks 93 ■ CountDownLatch 96 ConcurrentHashMap 97 ■ CopyOnWriteArrayList 99 Queues 102 4.4 Controlling execution 108 Modeling tasks 108 ■ ScheduledThreadPoolExecutor 110 4.5 The fork/join framework 111 A simple fork/join example 112 ■ ForkJoinTask and work stealing 114 ■ Parallelizing problems 115 4.6 The Java Memory Model (JMM) 116 4.7 Summary 118 Class files and bytecode 119 5 5.1 Classloading and class objects 120 Overview—loading and linking 120 ■ Verification 121 Class objects 122 ■ Classloaders 122 ■ Example—classloaders in Dependency Injection 124 5.2 Using method handles 125 MethodHandle 126 ■ MethodType 127 ■ Looking up method handles 127 ■ Example—reflection vs. proxies vs. MethodHandles 128 ■ Why choose MethodHandles? 131 5.3 Examining class files 132 Introducing javap 132 ■ Internal form for method signatures 132 ■ The constant pool 134 5.4 Bytecode 136 Example—disassembling a class 137 ■ The runtime environment 138 ■ Introduction to opcodes 140 Load and store opcodes 141 ■ Arithmetic opcodes 141 Execution control opcodes 142 ■ Invocation opcodes 143 Platform operation opcodes 143 ■ Shortcut opcode forms 144 Example—string concatenation 144 x CONTENTS 5.5 Invokedynamic 146 How invokedynamic works 146 ■ Example—disassembling an invokedynamic call 147 5.6 Summary 149 Understanding performance tuning 150 6 6.1 Performance terminology—some basic definitions 152 Latency 152 ■ Throughput 152 ■ Utilization 153 Efficiency 153 ■ Capacity 153 ■ Scalability 154 Degradation 154 6.2 A pragmatic approach to performance analysis 154 Know what you’re measuring 155 ■ Know how to take measurements 156 ■ Know what your performance goals are 157 ■ Know when to stop optimizing 157 Know the cost of higher performance 158 ■ Know the danger of premature optimization 158 6.3 What went wrong? Why we have to care 159 Moore’s Law—historic and future performance trends 160 Understanding the memory latency hierarchy 161 ■ Why is Java performance tuning hard? 162 6.4 A question of time—from the hardware up 163 Hardware clocks 163 ■ The trouble with nanoTime() 164 The role of time in performance tuning 166 ■ A case study— understanding cache misses 167 6.5 Garbage collection 169 Basics 170 ■ Mark and sweep 170 ■ jmap 172 Useful JVM parameters 176 ■ Reading the GC logs 177 Visualizing memory usage with VisualVM 178 Escape analysis 181 ■ Concurrent Mark-Sweep 182 G1—Java’s new collector 183 6.6 JIT compilation with HotSpot 184 Introduction to HotSpot 186 ■ Inlining methods 187 Dynamic compilation and monomorphic calls 188 Reading the compilation logs 188 6.7 Summary 190 CONTENTS xi PART 3 POLYGLOT PROGRAMMING ON THE JVM ........191 Alternative JVM languages 193 7 7.1 Java too clumsy? Them’s fighting words! 194 The reconciliation system 194 ■ Conceptual basics of functional programming 196 ■ Map and filter idioms 197 7.2 Language zoology 198 Interpreted vs. compiled languages 199 ■ Dynamic vs. static typing 199 ■ Imperative vs. functional languages 200 Reimplementation vs. original 201 7.3 Polyglot programming on the JVM 202 Why use a non-Java language? 203 Up-and-coming languages 204 7.4 How to choose a non-Java language for your project 205 Is the project area low-risk? 205 ■ Does the language interoperate well with Java? 206 ■ Is there good tooling and test support for the language? 207 ■ How hard is the language to learn? 207 Are there lots of developers using this language? 208 7.5 How the JVM supports alternative languages 208 Runtime environments for non-Java languages 209 Compiler fictions 209 7.6 Summary 211 Groovy: Java’s dynamic friend 213 8 8.1 Getting started with Groovy 215 Compiling and running 216 ■ Groovy console 217 8.2 Groovy 101—syntax and semantics 217 Default imports 219 ■ Numeric handling 219 Variables, dynamic versus static types, and scoping 220 Syntax for lists and maps 222 8.3 Differences from Java—traps for new players 223 Optional semicolons and return statements 224 Optional parentheses
Recommended publications
  • How Can Java Class Files Be Decompiled?
    HOW CAN JAVA CLASS FILES BE DECOMPILED? David Foster Chamblee High School 11th Grade Many computer science courses feature building a compiler as a final project. I have decided to take a spin on the idea and instead develop a decompiler. Specifically, I decided to write a Java decompiler because: one, I am already familiar with the Java language, two, the language syntax does not suffer from feature-bloat, and three, there do not appear to be many Java decompilers currently on the market. I have approached the task of writing a decompiler as a matter of translating between two different languages. In our case, the source language is Java Virtual Machine (VM) Bytecode, and the target language is the Java Language. As such, our decompiler will attempt to analyze the semantics of the bytecode and convert it into Java source code that has equivalent semantics. A nice sideeffect of this approach is that our decompiler will not be dependent upon the syntax of the bytecodes, the compiler used to generate the bytecodes, or the source language (possibly not Java). It will only care whether a class-file’s semantics can be represented in the Java language. Decompilation is divided up into six phases: 1. Read opcodes 2. Interpret opcode behavior 3. Identify Java-language “idioms” 4. Identify patterns of control-flow 5. Generate Java-language statements 6. Format and output to file The first four phases will be discussed in detail within this paper, as they were the primary focus of my research. Further details pertaining to these phases can be gleaned from the accompanying log book.
    [Show full text]
  • Advanced Programming for the Java(TM) 2 Platform
    Advanced Programming for the Java(TM) 2 Platform Training Index Advanced Programming for the JavaTM 2 Platform By Calvin Austin and Monica Pawlan November 1999 [CONTENTS] [NEXT>>] [DOWNLOAD] Requires login As an experienced developer on the JavaTM platform, you undoubtedly know how fast moving and comprehensive the Early Access platform is. Its many application programming interfaces (APIs) Downloads provide a wealth of functionality for all aspects of application and system-level programming. Real-world developers never use one Bug Database or two APIs to solve a problem, but bring together key Submit a Bug functionality spanning a number of APIs. Knowing which APIs you View Database need, which parts of which APIs you need, and how the APIs work together to create the best solution can be a daunting task. Newsletters Back Issues To help you navigate the Java APIs and fast-track your project Subscribe development time, this book includes the design, development, test, and deployment phases for an enterprise-worthy auction Learning Centers application. While the example application does not cover every Articles possible programming scenario, it explores many common Bookshelf situations and the discussions leave you with a solid methodology Code Samples for designing and building your own solutions. New to Java Question of the Week This book is for developers with more than a beginning level of Quizzes understanding of writing programs in the Java programming Tech Tips language. The example application is written with the Java® 2 Tutorials platform APIs and explained in terms of functional hows and whys, so if you need help installing the Java platform, setting up your Forums environment, or getting your first application to work, you should first read a more introductory book such as Essentials of the Java Programming Language: A Hands-On Guide or The Java Tutorial.
    [Show full text]
  • Information Retrieval from Java Archive Format
    Eötvös Loránd University Faculty of Informatics Department of Programming Languages and Compilers Information retrieval from Java archive format Supervisor: Author: Dr. Zoltán Porkoláb Bálint Kiss Associate Professor Computer Science MSc Budapest, 2017 Abstract During the course of my work, I contributed to CodeCompass, an open source code comprehension tool made for making codebase of software projects written in C, C++ and Java more understandable through navigation and visualization. I was tasked with the development of a module for recovering code information of Java classes in JAR files. This document details background concepts required for reverse- engineering Java bytecode, creating a prototype JAR file reader and how this solu- tion could be integrated to CodeCompass. First, I studied the structure of JAR format and how class files are stored in it. I looked into the Java Class file structure and how bytecode contained in class gets interpreted by the Java Virtual Machine. I also looked at existing decompilers and what bytecode libraries are. I created a proof-of-concept prototype that reads compiled classes from JAR file and extracts code information. I first showcased the use of Java Reflection API, then the use of Apache Commons Byte Code Engineering Library, a third-party bytecode library used for extracting and representing parts of Java class file as Java objects. Finally, I examined how CodeCompass works, how part of the prototype could be integrated into it and demonstrated the integration through parsing of a simple JAR file. i Acknowledgements I would like to thank Dr. Zoltán Porkoláb, Associate Professor of the Department of Programming Languages and Compilers at the Faculty of Informatics for admit- ting me to the CodeCompass project, supplying the thesis topic and helping with the documentation.
    [Show full text]
  • Java Class Annotation Example
    Java Class Annotation Example Bud etherealizing her matriarch inimitably, unwavering and decayed. Antimonious and regulation Rog violated almost anywhere, though Saunderson tosses his Creon outdating. Which Roland disinhuming so ordinarily that Westleigh tooth her opposites? It is class to classes are pretty easy to reflection to list to catch, company or property to generate mock for? First method of java example. The java are given list of bibliography. Default annotations example, java code examples of the compiler to be applied to json. The new project for extracting information to create web sites without editions but i go into the annotated bibliography paper, we welcome to isolate the mechanics of using. Parsing the examples can be used from open source and. We will utilize the class analyzes the same type declaration etc at runtime reflection methods or evaluative lists the suite itself which are. Nice explanation about the front controller, we added and then issues a class of the information, management example demonstrates how can be executed and. There are working standalone spring boot application into system proposed here, because of annotations. Its annotations example annotation examples java. Hibernate does not to class or specify java example of fundamental never hurt or not. Read from java class acts as each article has been designed with examples select then we learned about? We made as classes that class or examples of annotation example classes or an earlier article example it tells spring. The table pointing back to interface. From java example is applied only contains a second argument. Junit provides a test cases, we want specific warnings and ideas into our newsletter for an understanding takt time in.
    [Show full text]
  • Java and C I CSE 351 Autumn 2016
    L26: JVM CSE351, Spring 2018 Java Virtual Machine CSE 351 Spring 2018 Model of a Computer “Showing the Weather” Pencil and Crayon on Paper Matai Feldacker-Grossman, Age 4 May 22, 2018 L26: JVM CSE351, Spring 2018 Roadmap C: Java: Memory & data Integers & floats car *c = malloc(sizeof(car)); Car c = new Car(); x86 assembly c->miles = 100; c.setMiles(100); c->gals = 17; c.setGals(17); Procedures & stacks float mpg = get_mpg(c); float mpg = Executables free(c); c.getMPG(); Arrays & structs Memory & caches Assembly get_mpg: Processes language: pushq %rbp Virtual memory movq %rsp, %rbp ... Memory allocation popq %rbp Java vs. C ret OS: Machine 0111010000011000 code: 100011010000010000000010 1000100111000010 110000011111101000011111 Computer system: 2 L26: JVM CSE351, Spring 2018 Implementing Programming Languages Many choices in how to implement programming models We’ve talked about compilation, can also interpret Interpreting languages has a long history . Lisp, an early programming language, was interpreted Interpreters are still in common use: . Python, Javascript, Ruby, Matlab, PHP, Perl, … Interpreter Your source code implementation Your source code Binary executable Interpreter binary Hardware Hardware 3 L26: JVM CSE351, Spring 2018 An Interpreter is a Program Execute (something close to) the source code directly Simpler/no compiler – less translation More transparent to debug – less translation Easier to run on different architectures – runs in a simulated environment that exists only inside the interpreter process . Just port the interpreter (program), not the program-intepreted Slower and harder to optimize 4 L26: JVM CSE351, Spring 2018 Interpreter vs. Compiler An aspect of a language implementation . A language can have multiple implementations . Some might be compilers and other interpreters “Compiled languages” vs.
    [Show full text]
  • Hibernate Tools
    APPENDIX A ■ ■ ■ More Advanced Features In this appendix, we discuss some of the features that, strictly speaking, lie outside the scope of this book, but that you should be aware of if you go on to use Hibernate in more depth. Managed Versioning and Optimistic Locking While we have saved versioning for this appendix’s discussion of advanced features, it is actually quite straightforward to understand and apply. Consider the following scenario: • Client A loads and edits a record. • Client B loads and edits the same record. • Client A commits its edited record data. • Client B commits its differently edited record data. While the scenario is simple, the problems it presents are not. If Client A establishes a transaction, then Client B may not be able to load and edit the same record. Yet in a web environment, it is not unlikely that Client A will close a browser window on the open record, never committing or canceling the transaction, so that the record remains locked until the session times out. Clearly this is not a satisfactory solution. Usually, you will not want to permit the alternative scenario, in which no locking is used, and the last person to save a record wins! The solution, versioning, is essentially a type of optimistic locking (see Chapter 8). When any changes to an entity are stored, a version column is updated to reflect the fact that the entity has changed. When a subsequent user tries to commit changes to the same entity, the original version number will be compared against the current value—if they differ, the commit will be rejected.
    [Show full text]
  • Using Other Tools with Jython
    A P P E N D I X A Using Other Tools with Jython The primary focus of this appendix is to provide information on using some external Python packages with Jython, as well as providing information regarding the Jython registry. In some circumstances, the tools must be used or installed a bit differently on Jython than on CPython, and those differences will be noted. Because there is a good deal of documentation on the usage of these tools available on the web, this appendix will focus on using the tool specifically with Jython. However, relevant URLs will be cited for finding more documentation on each of the topics. The Jython Registry Because there is no good platform-independent equivalent of the Windows Registry or Unix environment variables, Java has its own environment variable namespace. Jython acquires its namespace from the following sources (later sources override defaults found in earlier places): • The Java system properties, typically passed in on the command line as options to the java interpreter. • The Jython “registry” file, containing prop=value pairs. Read on for the algorithm Jython uses to find the registry file. • The user’s personal registry file, containing similarly formatted prop/value pairs. The user’s registry file can be found at "user.home"+"/.jython" • Jython properties specified on the command line as options to the Jython class. See the -D option to the interpreter. Registry Properties The following properties are recognized by Jython. There may be others that aren’t documented here; consult the comments in registry file for details. python.cachedir The directory to use for caches—currently just package information.
    [Show full text]
  • Reversing Java (Malware) with Radare
    Reversing Java (Malware) with Radare Adam Pridgen April 2014 About me • Rice SecLab, a PhD Student • Independent InfoSec Consultant/Contractor Overview • Typical Java Reversing Talk o Decompile Code o Make Changes o Recompile and Win? • Java Malware: Fail! Overview Has this happened to you? Overview • IDA Pro 6.4 does not include meta-data Overview ● Malicious code analysis is hard ● Relevant information is key ● Tools assume code is complete or correct Overview ● Reversing JVM Bytecode viewed as a “simple” problem ○ Until you need to actually do it ○ Or you need to extract some type of information ● Too Long Didn’t Listen (tldl;) ○ Radare now supports basic class file manipulations ○ Hooking by rewriting class and method names ○ Manipulation of Access Flags ○ Inserting values in constant pool ○ More detailed inspection of files Multiple Command Extendible Multi-Language Architectures Based Components w/ Ctypes Open Source IL in progress Cross 2048 Platform Supports IO GDB Interface Hex Editor Web UI Layers Agenda • Discuss Java Class File and Format • Discuss Java Malware and Obfuscation • Introduce Java Reversing with Radare • Discuss Some Techniques • Conclude with Future Work Java Overview JVM Bytecode • ~203 Operations • Fairly easy to disassemble o Except for the built in “switch-tables” • JVM is Stack Based • Local Variables are stored in a local variable position JVM Bytecode • Caller copy the entire thread stack to caller • JVM resolves Class Name, Method Name, and argument types • Types are not important until they are important
    [Show full text]
  • Computer Language Processing (CS-320)
    Computer Language Processing (CS-320) Viktor Kuncak, EPFL https://lara.epfl.ch/w/cc Computer Language Processing = ? A language can be: I natural language (English, French, . ) I computer language (Scala, Java, C, SQL, . ) I language used to write mathematical statements: 8":9δ:8x: (jxj < δ ) jf (x)j < "j) We can define languages mathematically as sets of strings We can process languages: define algorithms working on strings In this course we study algorithms to process computer languages Interpreters and Compilers We are particularly interested in processing general-purpose programming languages. Two main approaches: I interpreter: execute instructions while traversing the program (Python) I compiler: traverse program, generate executable code to run later (Rust, C) Portable compiler (Java, Scala, C#): I compile (javac) to platform-independent bytecode (.class) I use a combination of interpretation and compilation to run bytecode (java) I compile or interpret fast, determine important code fragments (inner loops) I opt imize important code and swap it in for subsequent iterations Compilers for Programming Languages A typical compiler processes a Turing-complete programming language and translates it into the form where it can be efficiently executed (e.g. machine code). Source code in a programming language # compiler machine code I gcc, clang: map C into machine instructions I Java compiler: map Java source into bytecodes (.class files) I Just-in-time (JIT) compiler inside the Java Virtual Machine (JVM): translate .class files into machine
    [Show full text]
  • From Eiffel to the Java Virtual Machine
    From Eiffel to the Java Virtual Machine Adding a new language target to the EiffelStudio compiler Søren Engel, [email protected] Supervisor Dr. Joseph R. Kiniry Thesis submitted to The IT University of Copenhagen for the degree of Bachelor of Science in Software Development August 2012 Abstract Previous attemps has been made towards translating and executing programs written in Eiffel on the Java platform, as described in Baumgartner [1]. However, the generated Java code has not been easy to use in terms of interoperability between the two languages, due to the restrictions of the Java language. Due to the evolution of the Java language, the work presented in this thesis examines whether it is possible to simplify the translation model of Eiffel to Java. In doing so, this thesis describes a refined translation model that leverages on some of the new features of the Java language, such as the invokedynamic bytecode instruction. Moreover, in order to verify the correctness of the proposed translation model, a description follows on how the translation model may be integrated into the existing EiffelStudio compiler, in terms extending the back-end to target the Java platform. In regards of simplicity, it was found that by using new language features of Java, the translation model of Eiffel to Java could be simplified to the extend that it solves the known issues found in the solution presented in Baumgartner [1]. In trying to integrate the translation model into the existing EiffelStudio compiler, it was found that no public documentation exists which described the internal structure of the EiffelStudio compiler.
    [Show full text]
  • Programming in Java (Cspe-02)
    Master of Science(Cyber Security) (MSCS) PROGRAMMING IN JAVA (CSPE-02) Block 1 INTRODUCTION TO JAVA Unit – 1: Overview of Java Unit – 2: Key Features of Java Unit – 3: Operators Unit – 4: Control Statements Master of Science(Cyber Security) (MSCS) EXPERT COMMITTEE Dr. P.K Behera (Chairman) Reader in Computer Science Utkal University Bhubaneswar, Odisha Dr.J.RMohanty (Member) Professor and HOD KIIT University Bhubaneswar, Odisha Sri PabitranandaPattnaik (Member) Scientist-E, NIC Bhubaneswar, Odisha Sri Malaya Kumar Das (Member) Scientist-E, NIC Bhubaneswar, Odisha Dr. Bhagirathi Nayak (Member) Professor and Head (IT & System) Sri Sri University, Bhubaneswar,Odisha Dr.Manoranjan Pradhan (Member) Professor and Head (IT & System) G.I.T.A Bhubaneswar, Odisha Sri Chandrakant Mallick (Convener) Consultant (Academic) School of Computer and Information Science Odisha State Open University Sambalpur, Odisha Master of Science(Cyber Security) (MSCS) Course Writers Sunita Padhi Bijay Kumar Paikaray Centurion University of Technology and Management, Odisha Editor Aseem Kumar Patel Academic Consultant Odisha State Open University, Sambalpur, Odisha Material Production Dr. Jayanta Kar Sharma Registrar Odisha State Open University, Sambalpur © OSOU, 2017. Promoting Use and Contribution of Open Education Resources is made available under a Creative Commons Attribution- ShareAlike4.0http://creativecommons.org/licences/by-sa/4.0 Printers by : Sri Mandir Publication, Sahid Nagar, Bhubaneswar UNIT-1 Overview of Java Unit Structure 1.0 Introduction 1.1 Learning
    [Show full text]
  • Implementing Data-Flow Fusion DSL on Clojure
    CORE Metadata, citation and similar papers at core.ac.uk Provided by Hosei University Repository Implementing Data-Flow Fusion DSL on Clojure 著者 SAKURAI Yuuki 出版者 法政大学大学院情報科学研究科 journal or 法政大学大学院紀要. 情報科学研究科編 publication title volume 11 page range 1-6 year 2016-03-24 URL http://hdl.handle.net/10114/12212 Implementing Data-Flow Fusion DSL on Clojure Yuuki Sakuraiy Graduate School of Computer and Information Sciences, Hosei University, Tokyo, Japan [email protected] Abstract—This paper presents a new optimization tech- Hand fusion is powerful and sometime the fastest way, nique for programming language Clojure based on the stan- but this causes the problems of lowering the readability of dard fusion technique that merges list operations into a code. The modified code is often ugly and error prone. simplified loop. Automated fusion prevents such kind of code degrada- Short-cut fusions, foldr/build fusion, and stream fusions are tion. However, automated fusion can be applied only to standard fusion techniques used in a functional programming. limited cases. Moreover, a recent fusion technique proposed by Lippmeier. Our approach is the middle way between automatic Data flow fusion [7] can fuse loops containing several data and manual. The user of our system first insert data-flow consumers over stream operators on Haskell. However, this is fusion macro manually into the code, and then the Clojure only for Haskell. Clojure’s transducers [2] are factory func- macro processor takes care of fusion based on the data-flow tions generating abstract list objects. The functions generated by them wait evaluation as a lazy evaluation partially.
    [Show full text]