Pat Shaughnessy — «Ruby Under a Microscope

Total Page:16

File Type:pdf, Size:1020Kb

Pat Shaughnessy — «Ruby Under a Microscope How Ruby Works Ruby Under a Under the Hood a Microscope Under Ruby Ruby is a powerful programming language with How Ruby employs algorithms originally a focus on simplicity, but beneath its elegant developed for Lisp syntax it performs countless unseen tasks. How Ruby uses grammar rules to parse Microscope Ruby Under a Microscope gives you a and understand your code hands-on look at Ruby’s core, using extensive How your Ruby code is translated into a diagrams and thorough explanations to show different language by a compiler you how Ruby is implemented (no C skills required). Author Pat Shaughnessy takes No programming language needs to be a An Illustrated Guide a scientific approach, laying out a series of black box. Whether you’re already intrigued by experiments with Ruby code to take you behind language implementation or just want to dig to Ruby Internals the scenes of how programming languages deeper into Ruby, you’ll findRuby Under a work. You’ll even find information on JRuby Microscope a fascinating way to become and Rubinius (two alternative implementations a better programmer. of Ruby), as well as in-depth explorations of Pat Shaughnessy Ruby’s garbage collection algorithm. About the Author Ruby Under a Microscope will teach you: Well known for his coding expertise and passion for the Ruby programming language, How a few computer science concepts Pat Shaughnessy blogs and writes tutorials underpin Ruby’s complex implementation at http://patshaughnessy.net/. He also How Ruby executes your code using a develops Ruby applications at management virtual machine consulting firm McKinsey & Co. Shaughnessy is a regular presenter on the Ruby conference 10.times do |n| How classes and modules are the same circuit, and his articles and presentations have inside Ruby been featured in the Ruby Weekly newsletter, the Ruby5 podcast, and The Ruby Show. puts n Shaughnessy Covers Ruby 2.x, 1.9, and 1.8 end “I LIE FLAT.” This book uses RepKover — a durable binding that won’t snap shut. THE FINEST IN GEEK ENTERTAINMENT™ www.nostarch.com $39.95 ($41.95 CDN) Shelve In: Programming Languages/Ruby ADVANCE PRAISE FOR RUBY UNDER A MICROSCOPE “Many people have dug into the Ruby source code, but few make it back out and tell the tale as elegantly as Pat does in Ruby Under a Microscope! I particularly love the diagrams—and there are lots of them—as they make many opaque implementation topics a lot easier to understand, especially when coupled with Pat’s gentle narrative. This book is a delight for language implementation geeks and Rubyists with a penchant for dig- ging into the guts of their tools.” —PETER COOPER (@PETERC), EDITOR OF RUBY INSIDE AND RUBY WEEKLY “Man, this book was missing in the Ruby landscape—awesome content.” —XAVIER NORIA (@FXN), RUBY HERO, RUBY ON RAILS CORE TEAM MEMBER “Pat Shaughnessy did a tremendous job writing THE book about Ruby internals. Definitely a must read—you won’t find information like this anywhere else.” —SANTIAGO PASTORINO (@SPASTORINO), WYEWORKS CO-FOUNDER, RUBY ON RAILS CORE TEAM MEMBER “I really enjoyed the book and now have a far better understanding of both Ruby and CS. The writing made very complex topics (at least for me) very accessible, and I found the book hard to put down. Diagrams were awesome and are already popping in my head as I code. This is by far one of my top 3 favourite Ruby books.” —VLAD IVANOVIC (@VLADIIM), DIGITAL STRATEGIST AT HOLLER SYDNEY “While I’m not usually digging into Ruby Internals, this book was an absolutely awesome read.” —DAVID DERYL DOWNEY (@DAVIDDWDOWNEY), FOUNDER OF CYBERSPACE TEchNOLOGIES GROUP Ruby Under a Microscope An Illustrated Guide to Ruby Internals Pat Shaughnessy RUBY UNDER A MICROSCOPE. Copyright © 2014 by Patrick Shaughnessy. All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, elec- tronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. Printed in USA First printing 17 16 15 14 13 1 2 3 4 5 6 7 8 9 ISBN-10: 1-59327-527-7 ISBN-13: 978-1-59327-527-3 Publisher: William Pollock Production Editor: Riley Hoffman Cover Illustration: Charlie Wylie Interior Design: Octopod Studios Developmental Editor: William Pollock Technical Reviewer: Aaron Patterson Copyeditor: Julianne Jigour Compositors: Susan Glinert Stevens and Riley Hoffman Proofreader: Elaine Merrill For information on distribution, translations, or bulk sales, please contact No Starch Press, Inc. directly: No Starch Press, Inc. 245 8th Street, San Francisco, CA 94103 phone: 415.863.9900; fax: 415.863.9950; [email protected]; www.nostarch.com Library of Congress Cataloging-in-Publication Data Shaughnessy, Pat. Ruby under a microscope : an illustrated guide to Ruby internals / by Pat Shaughnessy. pages cm Summary: "An under-the-hood look at how the Ruby programming language runs code. Extensively illustrated with complete explanations and hands-on experiments. Covers Ruby 2.x"-- Provided by publisher. ISBN 978-1-59327-527-3 (paperback) -- ISBN 1-59327-527-7 (paperback) 1. Ruby (Computer program language) I. Title. QA76.73.R83S53 2013 005.1'17--dc23 2013030614 No Starch Press and the No Starch Press logo are registered trademarks of No Starch Press, Inc. Other product and company names mentioned herein may be the trademarks of their respective owners. Rather than use a trademark symbol with every occurrence of a trademarked name, we are using the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The information in this book is distributed on an “As Is” basis, without warranty. While every precaution has been taken in the preparation of this work, neither the author nor No Starch Press, Inc. shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in it. To my wife, Cristina; my daughter, Ana; and my son, Liam— thanks for supporting me all along. ABOUT THE AUTHOR Pat Shaughnessy is a Ruby developer working at McKinsey & Co., a management consulting firm. Pat was originally trained as a physicist at MIT, but later spent more than 20 years working as a software developer using C, Java, PHP, and Ruby, among other languages. Writing Ruby Under a Microscope has given him an excuse to reuse bits of his scientific training while studying Ruby. A fluent Spanish speaker, Pat frequently visits his wife’s family in northern Spain. He lives outside of Boston with his wife and two children. BRIEF CONTENTS Foreword by Aaron Patterson . xv Acknowledgments . xvii Introduction . xix Chapter 1: Tokenization and Parsing . 3 Chapter 2: Compilation . 31 Chapter 3: How Ruby Executes Your Code . 55 Chapter 4: Control Structures and Method Dispatch . 83 Chapter 5: Objects and Classes . 105 Chapter 6: Method Lookup and Constant Lookup . 133 Chapter 7: The Hash Table: The Workhorse of Ruby Internals . 167 Chapter 8: How Ruby Borrowed a Decades-Old Idea from Lisp . 191 Chapter 9: Metaprogramming . 219 Chapter 10: JRuby: Ruby on the JVM . 251 Chapter 11: Rubinius: Ruby Implemented with Ruby . 273 Chapter 12: Garbage Collection in MRI, JRuby, and Rubinius . 295 Index . 327 CONTENTS IN DETAIL FOREWORD by Aaron Patterson xv ACKNOWLEDGMENTS xvii INTRODUCTION xix Who This Book Is For . xx Using Ruby to Test Itself . xx Which Implementation of Ruby? . xxi Overview . xxi 1 TOKENIZATION AND PARSING 3 Tokens: The Words That Make Up the Ruby Language . 4 The parser_yylex Function . 8 Experiment 1-1: Using Ripper to Tokenize Different Ruby Scripts ................... 9 Parsing: How Ruby Understands Your Code . 12 Understanding the LALR Parse Algorithm . 13 Some Actual Ruby Grammar Rules . 20 Reading a Bison Grammar Rule . 22 Experiment 1-2: Using Ripper to Parse Different Ruby Scripts ..................... 23 Summary . 29 2 COMPILATION 31 No Compiler for Ruby 1 .8 . 32 Ruby 1 9. and 2 .0 Introduce a Compiler . 33 How Ruby Compiles a Simple Script . 34 Compiling a Call to a Block . 38 How Ruby Iterates Through the AST . 42 Experiment 2-1: Displaying YARV Instructions ................................ 44 The Local Table . 46 Compiling Optional Arguments . 48 Compiling Keyword Arguments . 49 Experiment 2-2: Displaying the Local Table .................................. 51 Summary . 53 3 HOW RUBY EXECUTES YOUR CODE 55 YARV’s Internal Stack and Your Ruby Stack . 56 Stepping Through How Ruby Executes a Simple Script . 58 Executing a Call to a Block . 61 Taking a Close Look at a YARV Instruction . 63 Experiment 3-1: Benchmarking Ruby 2.0 and Ruby 1.9 vs. Ruby 1.8 ............... 65 Local and Dynamic Access of Ruby Variables . 67 Local Variable Access . 67 Method Arguments Are Treated Like Local Variables . 70 Dynamic Variable Access . 71 Climbing the Environment Pointer Ladder in C . 74 Experiment 3-2: Exploring Special Variables ................................. 75 A Definitive List of Special Variables . 79 Summary . 81 4 CONTROL STRUCTURES AND METHOD DISPATCH 83 How Ruby Executes an if Statement . 84 Jumping from One Scope to Another . 86 Catch Tables . 88 Other Uses for Catch Tables . 90 Experiment 4-1: Testing How Ruby Implements for Loops Internally ................ 90 The send Instruction: Ruby’s Most Complex Control Structure . 92 Method Lookup and Method Dispatch . 92 Eleven Types of Ruby Methods . 93 Calling Normal Ruby Methods . 95 Preparing Arguments for Normal Ruby Methods . 95 Calling Built-In Ruby Methods . 97 Calling attr_reader and attr_writer . 97 Method Dispatch Optimizes attr_reader and attr_writer . 98 Experiment 4-2: Exploring How Ruby Implements Keyword Arguments .............. 99 Summary . 103 5 OBJECTS AND CLASSES 105 Inside a Ruby Object .
Recommended publications
  • Tomasz Dąbrowski / Rockhard GIC 2016 Poznań WHAT DO WE WANT? WHAT DO WE WANT?
    WHY (M)RUBY SHOULD BE YOUR NEXT SCRIPTING LANGUAGE? Tomasz Dąbrowski / Rockhard GIC 2016 Poznań WHAT DO WE WANT? WHAT DO WE WANT? • fast iteration times • easy modelling of complex gameplay logic & UI • not reinventing the wheel • mature tools • easy to integrate WHAT DO WE HAVE? MY PREVIOUS SETUP • Lua • not very popular outside gamedev (used to be general scripting language, but now most applications seem to use python instead) • even after many years I haven’t gotten used to its weird syntax (counting from one, global variables by default, etc) • no common standard - everybody uses Lua differently • standard library doesn’t include many common functions (ie. string.split) WHAT DO WE HAVE? • as of 2016, Lua is still a gold standard of general game scripting languages • C# (though not scripting) is probably even more popular because of the Unity • Unreal uses proprietary methods of scripting (UScript, Blueprints) • Squirrel is also quite popular (though nowhere near Lua) • AngelScript, Javascript (V8), Python… are possible yet very unpopular choices • and you can always just use C++ MY CRITERIA POPULARITY • popularity is not everything • but using a popular language has many advantages • most problems you will encounter have already been solved (many times) • more production-grade tools • more documentation, tutorials, books, etc • most problems you will encounter have already been solved (many times) • this literally means, that you will be able to have first prototype of anything in seconds by just copying and pasting code • (you can
    [Show full text]
  • TECHNICAL STANDARDS a Standards Validation Committee of Industry Representatives and Educators Reviewed and Updated These Standards on December 11, 2017
    SOFTWARE AND APP DESIGN 15.1200.40 TECHNICAL STANDARDS A Standards Validation Committee of industry representatives and educators reviewed and updated these standards on December 11, 2017. Completion of the program prepares students to meet the requirements of one or more industry certification: Cybersecurity Fundamentals Certificate, Oracle Certified Associate, Java SE 8 Programmer, Certified Internet Web (CIW) - JavaScript Specialist, CompTIA A+, CompTIA IT Fundamentals, CSX Cybersecurity Fundamentals Certificate, and Microsoft Technology Associate (MTA). The Arizona Career and Technical Education Quality Commission, the validating entity for the Arizona Skills Standards Assessment System, endorsed these standards on January 25, 2018. Note: Arizona’s Professional Skills are taught as an integral part of the Software and App Design program. The Technical Skills Assessment for Software and App Design is available SY2020-2021. Note: In this document i.e. explains or clarifies the content and e.g. provides examples of the content that must be taught. STANDARD 1.0 APPLY PROBLEM-SOLVING AND CRITICAL THINKING SKILLS 1.1 Establish objectives and outcomes for a task 1.2 Explain the process of decomposing a large programming problem into smaller, more manageable procedures 1.3 Explain “visualizing” as a problem-solving technique prior to writing code 1.4 Describe problem-solving and troubleshooting strategies applicable to software development STANDARD 2.0 RECOGNIZE SECURITY ISSUES 2.1 Identify common computer threats (e.g., viruses, phishing,
    [Show full text]
  • Konzeption Und Implementierung Eines Gamification Services Mit Ruby
    Konzeption und Implementierung eines Gamification Services mit Ruby Reinhard Buchinger MASTERARBEIT eingereicht am Fachhochschul-Masterstudiengang Interaktive Medien in Hagenberg im Dezember 2012 © Copyright 2012 Reinhard Buchinger Diese Arbeit wird unter den Bedingungen der Creative Commons Lizenz Namensnennung–NichtKommerziell–KeineBearbeitung Österreich (CC BY- NC-ND) veröffentlicht – siehe http://creativecommons.org/licenses/by-nc-nd/ 3.0/at/. ii Erklärung Ich erkläre eidesstattlich, dass ich die vorliegende Arbeit selbstständig und ohne fremde Hilfe verfasst, andere als die angegebenen Quellen nicht benutzt und die den benutzten Quellen entnommenen Stellen als solche gekennzeich- net habe. Die Arbeit wurde bisher in gleicher oder ähnlicher Form keiner anderen Prüfungsbehörde vorgelegt. Hagenberg, am 3. Dezember 2012 Reinhard Buchinger iii Inhaltsverzeichnis Erklärung iii Kurzfassung vii Abstract viii 1 Einleitung 1 1.1 Motivation und Zielsetzung . .1 1.2 Inhaltlicher Aufbau . .2 2 Grundlagen 3 2.1 Gamification . .3 2.1.1 Verfolgte Ziele . .3 2.1.2 Geläufige Spielemechanismen . .4 2.1.3 Frühere Formen . .4 2.2 Apache Cassandra . .6 2.2.1 Datenmodell im Vergleich zu RDBMS . .6 2.2.2 Vorteile im Clusterbetrieb . .7 2.3 Apache ZooKeeper . .7 2.4 RabbitMQ . .9 2.5 Memcached . 10 2.6 Ruby . 11 2.6.1 JRuby . 11 2.6.2 Gems . 12 2.7 Domänenspezifische Sprachen . 14 2.7.1 Vorteile . 14 2.7.2 Nachteile . 15 2.7.3 DSL in Ruby . 15 2.8 runtastic . 15 2.8.1 Produktpalette . 16 2.8.2 Infrastruktur . 16 3 Verwandte Systeme und Anforderungen 19 3.1 Verwandte Systeme . 19 iv Inhaltsverzeichnis v 3.1.1 Gamification Systeme .
    [Show full text]
  • AUTOMATIC DESIGN of NONCRYPTOGRAPHIC HASH FUNCTIONS USING GENETIC PROGRAMMING, Computational Intelligence, 4, 798– 831
    Universidad uc3m Carlos Ill 0 -Archivo de Madrid This is a postprint version of the following published document: Estébanez, C., Saez, Y., Recio, G., and Isasi, P. (2014), AUTOMATIC DESIGN OF NONCRYPTOGRAPHIC HASH FUNCTIONS USING GENETIC PROGRAMMING, Computational Intelligence, 4, 798– 831 DOI: https://doi.org/10.1111/coin.12033 © 2014 Wiley Periodicals, Inc. AUTOMATIC DESIGN OF NONCRYPTOGRAPHIC HASH FUNCTIONS USING GENETIC PROGRAMMING CESAR ESTEBANEZ, YAGO SAEZ, GUSTAVO RECIO, AND PEDRO ISASI Department of Computer Science, Universidad Carlos III de Madrid, Madrid, Spain Noncryptographic hash functions have an immense number of important practical applications owing to their powerful search properties. However, those properties critically depend on good designs: Inappropriately chosen hash functions are a very common source of performance losses. On the other hand, hash functions are difficult to design: They are extremely nonlinear and counterintuitive, and relationships between the variables are often intricate and obscure. In this work, we demonstrate the utility of genetic programming (GP) and avalanche effect to automatically generate noncryptographic hashes that can compete with state-of-the-art hash functions. We describe the design and implementation of our system, called GP-hash, and its fitness function, based on avalanche properties. Also, we experimentally identify good terminal and function sets and parameters for this task, providing interesting information for future research in this topic. Using GP-hash, we were able to generate two different families of noncryptographic hashes. These hashes are able to compete with a selection of the most important functions of the hashing literature, most of them widely used in the industry and created by world-class hashing experts with years of experience.
    [Show full text]
  • Open Source Used in Quantum SON Suite 18C
    Open Source Used In Cisco SON Suite R18C Cisco Systems, Inc. www.cisco.com Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices. Text Part Number: 78EE117C99-185964180 Open Source Used In Cisco SON Suite R18C 1 This document contains licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of any source code to which you may be entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License), please contact us at [email protected]. In your requests please include the following reference number 78EE117C99-185964180 Contents 1.1 argparse 1.2.1 1.1.1 Available under license 1.2 blinker 1.3 1.2.1 Available under license 1.3 Boost 1.35.0 1.3.1 Available under license 1.4 Bunch 1.0.1 1.4.1 Available under license 1.5 colorama 0.2.4 1.5.1 Available under license 1.6 colorlog 0.6.0 1.6.1 Available under license 1.7 coverage 3.5.1 1.7.1 Available under license 1.8 cssmin 0.1.4 1.8.1 Available under license 1.9 cyrus-sasl 2.1.26 1.9.1 Available under license 1.10 cyrus-sasl/apsl subpart 2.1.26 1.10.1 Available under license 1.11 cyrus-sasl/cmu subpart 2.1.26 1.11.1 Notifications 1.11.2 Available under license 1.12 cyrus-sasl/eric young subpart 2.1.26 1.12.1 Notifications 1.12.2 Available under license Open Source Used In Cisco SON Suite R18C 2 1.13 distribute 0.6.34
    [Show full text]
  • Rubyperf.Pdf
    Ruby Performance. Tips, Tricks & Hacks Who am I? • Ezra Zygmuntowicz (zig-mun-tuv-itch) • Rubyist for 4 years • Engine Yard Founder and Architect • Blog: http://brainspl.at Ruby is Slow Ruby is Slow?!? Well, yes and no. The Ruby Performance Dichotomy Framework Code VS Application Code Benchmarking: The only way to really know performance characteristics Profiling: Measure don’t guess. ruby-prof What is all this good for in real life? Merb Merb Like most useful code it started as a hack, Merb == Mongrel + Erb • No cgi.rb !! • Clean room implementation of ActionPack • Thread Safe with configurable Mutex Locks • Rails compatible REST routing • No Magic( well less anyway ;) • Did I mention no cgi.rb? • Fast! On average 2-4 times faster than rails Design Goals • Small core framework for the VC in MVC • ORM agnostic, use ActiveRecord, Sequel, DataMapper or roll your own db access. • Prefer simple code over magic code • Keep the stack traces short( I’m looking at you alias_method_chain) • Thread safe, reentrant code Merb Hello World No code is faster then no code • Simplicity and clarity trumps magic every time. • When in doubt leave it out. • Core framework to stay small and simple and easy to extend without gross hacks • Prefer plugins for non core functionality • Plugins can be gems Key Differences • No auto-render. The return value of your controller actions is what gets returned to client • Merb’s render method just returns a string, allowing for multiple renders and more flexibility • PartController’s allow for encapsualted applets without big performance cost Why not work on Rails instead of making a new framework? • Originally I was trying to optimize Rails and make it more thread safe.
    [Show full text]
  • Implementation of the Programming Language Dino – a Case Study in Dynamic Language Performance
    Implementation of the Programming Language Dino – A Case Study in Dynamic Language Performance Vladimir N. Makarov Red Hat [email protected] Abstract design of the language, its type system and particular features such The article gives a brief overview of the current state of program- as multithreading, heterogeneous extensible arrays, array slices, ming language Dino in order to see where its stands between other associative tables, first-class functions, pattern-matching, as well dynamic programming languages. Then it describes the current im- as Dino’s unique approach to class inheritance via the ‘use’ class plementation, used tools and major implementation decisions in- composition operator. cluding how to implement a stable, portable and simple JIT com- The second part of the article describes Dino’s implementation. piler. We outline the overall structure of the Dino interpreter and just- We study the effect of major implementation decisions on the in-time compiler (JIT) and the design of the byte code and major performance of Dino on x86-64, AARCH64, and Powerpc64. In optimizations. We also describe implementation details such as brief, the performance of some model benchmark on x86-64 was the garbage collection system, the algorithms underlying Dino’s improved by 3.1 times after moving from a stack based virtual data structures, Dino’s built-in profiling system, and the various machine to a register-transfer architecture, a further 1.5 times by tools and libraries used in the implementation. Our goal is to give adding byte code combining, a further 2.3 times through the use an overview of the major implementation decisions involved in of JIT, and a further 4.4 times by performing type inference with a dynamic language, including how to implement a stable and byte code specialization, with a resulting overall performance im- portable JIT.
    [Show full text]
  • Feather-Weight Cloud OS Developed Within 14 Man-Days Who Am I ?
    Mocloudos Feather-weight Cloud OS developed within 14 man-days Who am I ? • Embedded Software Engineer • OSS developer • Working at Monami-ya LLC. • Founder/CEO/CTO/CFO/and some more. Some My Works • Realtime OS • TOPPERS/FI4 (dev lead) • TOPPERS/HRP (dev member) • OSS (C) JAXA (C) TOPPERS Project • GDB (committer / write after approval) • mruby (listed in AUTHOR file) • Android-x86 (develop member) Wish • Feather-weight cloud OS. • Runs on virtualization framework. • Works with VM based Light-weight Language like Ruby. Wish • Construct my Cloud OS within 14 man-days My First Choice • mruby - http://www.mruby.org/ • Xen + Stubdom - http://www.xen.org/ What’s mruby • New Ruby runtime. http://github.com/mruby/mruby/ • Created by Matz. GitHub based CI development. • Embedded systems oriented. • Small memory footprint. • High portability. (Device independent. ISO C99 style.) • Multiple VM state support (like Lua). • mrbgem - component model. mrbgem • Simple component system for mruby. • Adds/modifies your feature to mruby core. • By writing C lang source or Ruby script. • Linked statically to core runtime. • Easy to validate whole runtime statically. Stubdom • “Stub” for Xen instances in DomU. • IPv4 network support (with LWIP stack) • Block devices support. • Newlib based POSIX emulation (partly) • Device-File abstraction like VFS. Stubdom • This is just a stub. • The implementation is half baked. • More system calls returns just -1 (error) • No filesystems My Additional Choice • FatFs : Free-beer FAT Filesystem • http://elm-chan.org/fsw/ff/00index_e.html • Very permissive license. • So many example uses including commercial products. My Hacks • Writing several glue code as mrbgems. • Xen’s block device - FatFs - Stubdom • Hacking mrbgems to fit poor Stubdom API set.
    [Show full text]
  • Insert Here Your Thesis' Task
    Insert here your thesis' task. Czech Technical University in Prague Faculty of Information Technology Department of Software Engineering Master's thesis New Ruby parser and AST for SmallRuby Bc. Jiˇr´ıFajman Supervisor: Ing. Marcel Hlopko 18th February 2016 Acknowledgements I would like to thank to my supervisor Ing. Marcel Hlopko for perfect coop- eration and valuable advices. I would also like to thank to my family for support. Declaration I hereby declare that the presented thesis is my own work and that I have cited all sources of information in accordance with the Guideline for adhering to ethical principles when elaborating an academic final thesis. I acknowledge that my thesis is subject to the rights and obligations stip- ulated by the Act No. 121/2000 Coll., the Copyright Act, as amended. In accordance with Article 46(6) of the Act, I hereby grant a nonexclusive au- thorization (license) to utilize this thesis, including any and all computer pro- grams incorporated therein or attached thereto and all corresponding docu- mentation (hereinafter collectively referred to as the \Work"), to any and all persons that wish to utilize the Work. Such persons are entitled to use the Work in any way (including for-profit purposes) that does not detract from its value. This authorization is not limited in terms of time, location and quan- tity. However, all persons that makes use of the above license shall be obliged to grant a license at least in the same scope as defined above with respect to each and every work that is created (wholly or in part) based on the Work, by modifying the Work, by combining the Work with another work, by including the Work in a collection of works or by adapting the Work (including trans- lation), and at the same time make available the source code of such work at least in a way and scope that are comparable to the way and scope in which the source code of the Work is made available.
    [Show full text]
  • User Guide for HCR Estimator 2.0: Software to Calculate Cost and Revenue Thresholds for Harvesting Small-Diameter Ponderosa Pine
    United States Department of Agriculture User Guide for HCR Forest Service Estimator 2.0: Software Pacific Northwest Research Station to Calculate Cost and General Technical Report PNW-GTR-748 Revenue Thresholds April 2008 for Harvesting Small- Diameter Ponderosa Pine Dennis R. Becker, Debra Larson, Eini C. Lowell, and Robert B. Rummer The Forest Service of the U.S. Department of Agriculture is dedicated to the principle of multiple use management of the Nation’s forest resources for sustained yields of wood, water, forage, wildlife, and recreation. Through forestry research, cooperation with the States and private forest owners, and management of the National Forests and National Grasslands, it strives—as directed by Congress—to provide increasingly greater service to a growing Nation. The U.S. Department of Agriculture (USDA) prohibits discrimination in all its programs and activities on the basis of race, color, national origin, age, disability, and where applicable, sex, marital status, familial status, parental status, religion, sexual orientation, genetic information, political beliefs, reprisal, or because all or part of an individual’s income is derived from any public assistance program. (Not all prohibited bases apply to all programs.) Persons with disabilities who require alternative means for communication of program information (Braille, large print, audiotape, etc.) should contact USDA’s TARGET Center at (202) 720-2600 (voice and TDD). To file a complaint of discrimination, write USDA, Director, Office of Civil Rights, 1400 Independence Avenue, SW, Washington, DC 20250-9410 or call (800) 795-3272 (voice) or (202) 720-6382 (TDD). USDA is an equal opportunity provider and employer. Authors Dennis R.
    [Show full text]
  • Cross-Platform Mobile Software Development with React Native Pages and Ap- Pendix Pages 27 + 0
    Cross-platform mobile software development with React Native Janne Warén Bachelor’s thesis Degree Programme in ICT 2016 Abstract 9.10.2016 Author Janne Warén Degree programme Business Information Technology Thesis title Number of Cross-platform mobile software development with React Native pages and ap- pendix pages 27 + 0 The purpose of this study was to give an understanding of what React Native is and how it can be used to develop a cross-platform mobile application. The study explains the idea and key features of React Native based on source literature. The key features covered are the Virtual DOM, components, JSX, props and state. I found out that React Native is easy to get started with, and that it’s well-suited for a web programmer. It makes the development process for mobile programming a lot easier com- pared to traditional native approach, it’s easy to see why it has gained popularity fast. However, React Native still a new technology under rapid development, and to fully under- stand what’s happening it would be good to have some knowledge of JavaScript and per- haps React (for the Web) before jumping into React Native. Keywords React Native, Mobile application development, React, JavaScript, API Table of contents 1 Introduction ..................................................................................................................... 1 1.1 Goals and restrictions ............................................................................................. 1 1.2 Definitions and abbreviations ................................................................................
    [Show full text]
  • Internationalization in Ruby 2.4
    Internationalization in Ruby 2.4 http://www.sw.it.aoyama.ac.jp/2016/pub/IUC40-Ruby2.4/ 40th Internationalization and Unicode Conference Santa Clara, California, U.S.A., November 3, 2016 Martin J. DÜRST [email protected] Aoyama Gakuin University © 2016 Martin J. Dürst, Aoyama Gakuin University Abstract Ruby is a purely object-oriented scripting language which is easy to learn for beginners and highly appreciated by experts for its productivity and depth. This presentation discusses the progress of adding internationalization functionality to Ruby for the version 2.4 release expected towards the end of 2016. One focus of the talk will be the currently ongoing implementation of locale-aware case conversion. Since Ruby 1.9, Ruby has a pervasive if somewhat unique framework for character encoding, allowing different applications to choose different internationalization models. In practice, Ruby is most often and most conveniently used with UTF-8. Support for internationalization facilities beyond character encoding has been available via various external libraries. As a result, applications may use conflicting and confusing ways to invoke internationalization functionality. To use case conversion as an example, up to version 2.3, Ruby comes with built-in methods for upcasing and downcasing strings, but these only work on ASCII. Our implementation extends this to the whole Unicode range for version 2.4, and efficiently reuses data already available for case-sensitive matching in regular expressions. We study the interface of internationalization functions/methods in a wide range of programming languages and Ruby libraries. Based on this study, we propose to extend the current built-in Ruby methods, e.g.
    [Show full text]