Introduction (0A)

Total Page:16

File Type:pdf, Size:1020Kb

Introduction (0A) Introduction (0A) Introduction Young Won Lim 1 9/3/14 Copyright (c) 2011-= 2014 Young W. Lim. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Please send corrections (or suggestions) to [email protected]. This document was produced by using OpenOffice. Introduction Young Won Lim 2 9/3/14 Java source files Python source files (.java) (.py) class Foo { def f(x): /* ... */ print x } ... javac jython JVM (Java Virtual Machine) Java bytecode files Java bytecode files (.class/.jar) (.class/.jar) ... ... iconst_0 istore_1 iaload iload_1 istore_1 jsr 19 jsr 19 iconst_0 Java source files Python source files iload_1 iaload (.java) (.py) ... ... class Foo { def f(x): /* ... */ print x } ... Intel x86 JVM ARM JVM Bytecode Bytecode verifier verifier javac jython Memory Memory manager manager JRE (garbage Interpreter / JRE (garbage Interpreter / Java bytecode files Java bytecode files collection) JIT compiler collection) JIT compiler (.class/.jar) (.class/.jar) ... ... iconst_0 istore_1 iaload iload_1 Java APIs Java APIs istore_1 jsr 19 jsr 19 iconst_0 PC Operating system Mobile Operating system iload_1 iaload ... ... CrackBerry 1 Q 2 W 3 O P E R T Y U I 4 A 5 6 ← S D F G H J K L alt 7 8 9 | Z X C V B N M $ aA 0 space SYM aA Intel x86 JVM ARM JVM Bytecode Bytecode verifier verifier Memory Memory http://en.wikipedia.org/ manager manager JRE (garbage Interpreter / JRE (garbage Interpreter / collection) JIT compiler collection) JIT compiler Young Won Lim Class 3 7/21/09 Java APIs Java APIs PC Operating system Mobile Operating system CrackBerry 1 2 Q W 3 O P E R T Y U I 4 5 A S 6 ← D F G H J K L alt 7 8 9 | Z X C V B N M $ aA 0 space SYM aA Java Bytecode A Java virtual machine (JVM) a process virtual machine that executes Java bytecode. The code execution component of the Java platform. Java bytecode the instruction set of the Java virtual machine. for a instruction (opcode), 1 ~ 2 bytes for passing parameters, 0+ bytes The 256 possible byte-long opcodes 198 are currently in use 51 are reserved for future use 3 are set aside as permanently unimplemented an opcode (operation code) the portion of a machine language instruction that specifies the operation to be performed. http://en.wikipedia.org/ Young Won Lim Class 4 7/21/09 Java Bytecode Instructions Instructions fall into a number of broad groups: Load and store (e.g. aload_0, istore) Arithmetic and logic (e.g. ladd, fcmpl) Type conversion (e.g. i2b, d2i) Object creation and manipulation (new, putfield) Operand stack management (e.g. swap, dup2) Control transfer (e.g. ifeq, goto) Method invocation and return (e.g. invokespecial, areturn) http://en.wikipedia.org/ Young Won Lim Class 5 7/21/09 javac javac http://en.wikipedia.org/ Young Won Lim Class 6 7/21/09 Machine Code Machine code or machine language a set of instructions executed directly by a computer's central processing unit (CPU). a load, a jump, or an ALU operation on a unit of data in a CPU register or memory. Every program directly executed by a CPU is made up of a series of such instructions. http://en.wikipedia.org/ Young Won Lim Class 7 7/21/09 MIPS Machine Code Examples http://en.wikipedia.org/ Young Won Lim Class 8 7/21/09 Intel Assembly Language Examples http://en.wikipedia.org/ Young Won Lim Class 9 7/21/09 Java Class File Java class file a file with the .class filename extension containing a Java bytecode produced by Java compiler from Java programming language source files (.java files) containing Java classes. If a source file has more than one class, each class is compiled into a separate class file. http://en.wikipedia.org/ Young Won Lim Class 10 7/21/09 Java Platform API JVM Young Won Lim Class 11 7/21/09 Java Edition Java EE Java SE Java ME JVM Java ME VM Java Card Java Card VM Java FX Young Won Lim Class 12 7/21/09 Java Programs Java Applications Java Applet Java Sublet Android Application Java Server Page Java Beans Young Won Lim Class 13 7/21/09 JDK & JRE Java Development Kit Java Runtime Environment Young Won Lim Class 14 7/21/09 References [1] Java in a nutshell, 4th ed, David Flanagan [2] An Introduction to Object-Oriented Programming with Java, C. Thomas, Wu [3] Power Java, I. K. Chun (in Korean) Introduction Young Won Lim 15 9/3/14.
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]
  • Scala: a Functional, Object-Oriented Language COEN 171 Darren Atkinson What Is Scala? — Scala Stands for Scalable Language — It Was Created in 2004 by Martin Odersky
    Scala: A Functional, Object-Oriented Language COEN 171 Darren Atkinson What is Scala? Scala stands for Scalable Language It was created in 2004 by Martin Odersky. It was designed to grow with the demands of its users. It was designed to overcome many criticisms of Java. It is compiled to Java bytecode and is interoperable with existing Java classes and libraries. It is more of a high-level language than Java, having higher- order containers and iteration constructs built-in. It encourages a functional programming style, much like ML and Scheme. It also has advanced object-oriented features, much like Java and C++. Using Scala Using Scala is much like using Python or ML, and is not as unwieldy as using Java. The Scala interpreter can be invoked directly from the command line: $ scala Welcome to Scala 2.11.8 scala> println("Hi!") The Scala interpreter can also be given a file on the command line to execute: $ scala foo.scala Scala Syntax Scala has a Java-like syntax with braces. The assignment operator is simply =. Strings are built-in and use + for concatenation. Indexing is done using ( ) rather than [ ]. The first index is index zero. Parameterized types use [ ] rather than < >. A semicolon is inferred at the end of a line. However, since it is functional, everything is an expression and there are no “statements”. Scala Types In Java, the primitive types are not objects and wrapper classes must be used. Integer for int, Boolean for bool, etc. In Scala, everything is an object including the more “primitive” types. The Scala types are Int, Boolean, String, etc.
    [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]
  • Nashorn Architecture and Performance Improvements in the Upcoming JDK 8U40 Release
    Oracle Blogs Home Products & Services Downloads Support Partners Communities About Login Oracle Blog Nashorn JavaScript for the JVM. Nashorn architecture and performance improvements in the upcoming JDK 8u40 release By lagergren on Dec 12, 2014 Hello everyone! We've been bad att blogging here for a while. Apologizes for that. I thought it would be prudent to talk a little bit about OpenJDK 8u40 which is now code frozen, and what enhancements we have made for Nashorn. 8u40 includes a total rewrite of the Nashorn code generator, which now contains the optimistic type system. JavaScript, or any dynamic language for that matter, doesn't have enough statically available type information to provide performant code, just by doing compile time analysis. That's why we have designed the new type system to get around this performance bottleneck. While Java bytecode, which is the output of the Nashorn JIT, is strongly typed and JavaScript isn't, there are problems translating the AST to optimal bytecode. Attila Szegedi, Hannes Wallnöfer and myself have spent significant time researching and implementing this the last year. Background: Conservatively, when implementing a JavaScript runtime in Java, anything known to be a number can be represented in Java as a double, and everything else can be represented as an Object. This includes numbers, ints, longs and other primitive types that aren't statically provable. Needless to say, this approach leads to a lot of internal boxing, which is quite a bottleneck for dynamic language execution speed on the JVM. The JVM is very good at optimizing Java-like bytecode, and this is not Java-like bytecode.
    [Show full text]
  • Java in Embedded Linux Systems
    Java in Embedded Linux Systems Java in Embedded Linux Systems Thomas Petazzoni / Michael Opdenacker Free Electrons http://free-electrons.com/ Created with OpenOffice.org 2.x Java in Embedded Linux Systems © Copyright 2004-2007, Free Electrons, Creative Commons Attribution-ShareAlike 2.5 license http://free-electrons.com Sep 15, 2009 1 Rights to copy Attribution ± ShareAlike 2.5 © Copyright 2004-2008 You are free Free Electrons to copy, distribute, display, and perform the work [email protected] to make derivative works to make commercial use of the work Document sources, updates and translations: Under the following conditions http://free-electrons.com/articles/java Attribution. You must give the original author credit. Corrections, suggestions, contributions and Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license translations are welcome! identical to this one. For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. License text: http://creativecommons.org/licenses/by-sa/2.5/legalcode Java in Embedded Linux Systems © Copyright 2004-2007, Free Electrons, Creative Commons Attribution-ShareAlike 2.5 license http://free-electrons.com Sep 15, 2009 2 Best viewed with... This document is best viewed with a recent PDF reader or with OpenOffice.org itself! Take advantage of internal
    [Show full text]
  • Evaluation of Clojure, Java, and Scala
    Evaluation of Clojure, Java, and Scala Analysis of Programming Languages ­ TTÜ Toke Abildgaard von Ryberg 10.12.2015 Evaluation of Clojure, Java, and Scala 10.12.2015 Analysis of Programming Languages Toke Abildgaard von Ryberg Introduction Java Virtual Machine Java Scala Clojure Programming languages evaluation Essential characteristics Well defined syntactic and semantic definition of language Reliability Fast translation Machine independence Desirable characteristics Generality Consistency with commonly used notations Uniformity Extensibility (ease to add features) Summary References 2 Evaluation of Clojure, Java, and Scala 10.12.2015 Analysis of Programming Languages Toke Abildgaard von Ryberg Introduction In this paper I will evaluate three languages that all uses Java Virtual Machine (JVM). The three languages are Clojure, Java, and Scala. First, I will briefly describe JVM and the three languages. Then I will evaluate the languages based on essential characteristics and desirable characteristics. The essential characteristics I use for evaluating programming languages are: ● Well defined syntactic and semantic definition of language ● Reliability ● Fast translation ● Machine independence The desirable characteristics are: ● Generality ● Consistency with commonly used notations ● Uniformity ● Extensibility (ease to add features) Java Virtual Machine1 The Java Virtual Machine(JVM) is a virtual machine used for executing Java bytecode. JVM is part of Java Runtime Environment(JRE) along with Java Class library. JRE is available on multiple platforms including Windows, Mac OS X, and Linux. The features of JVM include garbage collection and a JIT compiler. A programming language with functionality expressed in valid class files and able to be hosted by JVM is called a JVM language. When choosing to create a new programming language one might choose to create a JVM language to take advantage of the features of JVM.
    [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]
  • Design and Analysis of a Scala Benchmark Suite for the Java Virtual Machine
    Design and Analysis of a Scala Benchmark Suite for the Java Virtual Machine Entwurf und Analyse einer Scala Benchmark Suite für die Java Virtual Machine Zur Erlangung des akademischen Grades Doktor-Ingenieur (Dr.-Ing.) genehmigte Dissertation von Diplom-Mathematiker Andreas Sewe aus Twistringen, Deutschland April 2013 — Darmstadt — D 17 Fachbereich Informatik Fachgebiet Softwaretechnik Design and Analysis of a Scala Benchmark Suite for the Java Virtual Machine Entwurf und Analyse einer Scala Benchmark Suite für die Java Virtual Machine Genehmigte Dissertation von Diplom-Mathematiker Andreas Sewe aus Twistrin- gen, Deutschland 1. Gutachten: Prof. Dr.-Ing. Ermira Mezini 2. Gutachten: Prof. Richard E. Jones Tag der Einreichung: 17. August 2012 Tag der Prüfung: 29. Oktober 2012 Darmstadt — D 17 For Bettina Academic Résumé November 2007 – October 2012 Doctoral studies at the chair of Prof. Dr.-Ing. Er- mira Mezini, Fachgebiet Softwaretechnik, Fachbereich Informatik, Techni- sche Universität Darmstadt October 2001 – October 2007 Studies in mathematics with a special focus on com- puter science (Mathematik mit Schwerpunkt Informatik) at Technische Uni- versität Darmstadt, finishing with a degree of Diplom-Mathematiker (Dipl.- Math.) iii Acknowledgements First and foremost, I would like to thank Mira Mezini, my thesis supervisor, for pro- viding me with the opportunity and freedom to pursue my research, as condensed into the thesis you now hold in your hands. Her experience and her insights did much to improve my research as did her invaluable ability to ask the right questions at the right time. I would also like to thank Richard Jones for taking the time to act as secondary reviewer of this thesis.
    [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]