DOCSLIB.ORG

A.Data and Methods. B.Information Hiding. C.Classes. Da

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A.Data and Methods. B.Information Hiding. C.Classes. Da Java How to Program, 5/e Test Item File 1 of 5 Chapter 8 Section 8.1 8.1 Q1: Object-Oriented Programming encapsulates: a.Data and methods. b.Information hiding. c.Classes. d.Adjectives ANS: a. Data and methods Section 8.2 8.2 Q1: If class A extends B, then: a.Class A is the base class. b.Class A is the superclass. c.Class A inherits from class B. d.Class B is the derived class. ANS: c. Class A inherits from class B. Class B is the base class or superclass. Class A is the derived class or subclass. 8.2 Q2: Constructors: a.Have the same name as the class. b.May not specify a return type. c.Initialize objects of a class. d.All of the above. ANS: d. All of the above. Section 8.3 8.3 Q1: An instance variable is hidden in the scope of a method when a.The instance variable has the same name as the method. b.The instance variable has the same name as a local variable in the method. c.The instance variable has the same name as the class. d.The instance variable has the same name as the file. ANS: b. The instance variable has the same name as a local variable in the method. 8.3 Q2: Which of the following statements is true? a.Within a class’s scope, class members are accessible to all of that class’s methods, but cannot be referenced directly by name. b.It is a syntax error if a method declares a local variable with the same name as a variable declared in the method’s enclosing class. c.Variables declared in a method are known only to that method. d.None of the above. ANS: c. Variables declared in method are know only to that method. Section 8.4 8.4 Q1: Which of the following should usually be private? a.Methods. b.Constructors. c.Variables (or fields). d.All of the above. ANS: c. Variables (or fields). 8.4 Q2: Which of the following statements is true? a.Methods and instance variables can both be either public or private. b.Information hiding is achieved by restricting access to class members via keyword public. c.The private members of a class are directly accessible to the client of a class. d.None of the above is true. ANS: a. Methods and instance variables can both be either public or private. © Copyright 2003 by Deitel & Associates, Inc. and Prentice Hall. All Rights Reserved. Java How to Program, 5/e Test Item File 2 of 5 Section 8.5: 8.5 Q1: When should a program explicitly use the this reference: a.Accessing a private variable. b.Accessing a public variable. c.Accessing a local variable. d.Accessing a field that is shadowed by a local variable. ANS: c. Accessing a field that is shadowed by a local variable. 8.5 Q2: Having a this reference allows: a.A method refer explicitly to the instance variables and other methods of the object on which the method was called. b.A method to refer implicitly to the instance variables and other methods of the object on which the method was called. c.An object to reference itself. d.All of the above. ANS: d. All of the above. Section 8.6 8.6 Q1: A constructor cannot: a.Be overloaded. b.Initialize variables to their defaults. c.Specify return types or return values. d.Have the same name as the class. ANS: c. Specify return types or return values. 8.6 Q2: Which of the following will be used to create an instance of a class if the programmer does not define a constructor? a.A default constructor. b.An overloaded constructor. c.The Object class constructor with the name of the desired class passed in as an argument. d.If no constructor is written, then one isn’t needed. ANS: a. A default constructor. Section 8.7 8.7 Q1: Constructors: a.Initialize instance variables. b.When overloaded, can have identical argument lists. c.When overloaded, are selected by number and types of parameters. d.a and c. ANS: d. a and c. 8.7 Q2: A well-designed group of constructors: a.Guarantee the object is created in a consistent state. b.May call common methods. c.Allows the class's user flexibility in specifying some or all of the initial instance variable values. d.All of the above. ANS d. All of the above. Section 8.8 8.8 Q1: Not using set and get methods is: a.A syntax error. b.A logic error. c.Not good program design. d.None of the above. ANS: c. Not good program design. © Copyright 2003 by Deitel & Associates, Inc. and Prentice Hall. All Rights Reserved. Java How to Program, 5/e Test Item File 3 of 5 8.8 Q2: Using public set methods provides data integrity if: a.The instance variables are public. b.The instance variables are private. c.The programmer provides validity checking. d.Both b and c. ANS: d. Both b and c. Section 8.9 8.9 Q1: Composition: a.Is a form of software reuse. b.Is using an object reference as a class member. c.Is a good design practice. d.All of the above. ANS: d. All of the above. Section 8.10 8.10 Q1: Which of the following is not true? a.Finalizer methods typically return resources to the system. b.Memory leaks using Java are rare because of garbage collection. c.Objects are marked for garbage collection by the finalizer. d.The garbage collector reclaims unused memory. ANS: c. Objects are marked for garbage collection by the finalizer. Object are marked for garbage collection when there are no more references to the object Section 8.11 8.11 Q1: Static class variables: a.Are final. b.Are public. c.Are private. d.Are shared by all objects of a class. ANS: d. Are shared by all objects of a class. 8.11 Q2: Which of the following is not true? a.A static method must be used to access private static instance variables. b.A static method has no this reference. c.A static method can be accessed even when no objects of its class have been instantiated. d.A static method can call instance methods directly. ANS: d. A static method can call instance methods directly. Section 8.12 8.12 Q1: Instance variables declared final do not or cannot: a.Use the principle of least privilege. b.Be initialized. c.Be modified. d.Cause syntax errors if used as a left-hand value. ANS: c. Be modified. Section 8.13 8.13 Q1: A package is: a.A directory structure used to organize classes and interfaces. © Copyright 2003 by Deitel & Associates, Inc. and Prentice Hall. All Rights Reserved. Java How to Program, 5/e Test Item File 4 of 5 b.A mechanism for software reuse. c.A group of related classes and interfaces. d.All of the above. ANS: d. All of the above. 8.13 Q2: A class within a package must be declared public if a.It will only be used by other classes in the same package. b.It will be used by classes that are not in the same package. c.It is in the same directory as the other classes in the package. d.It has a unique name. ANS: b. It will be used by classes that are not in the same package. Classes outside the package cannot use a class if the class is not declared public. 8.13 Q3: Consider the statement package com.deitel.jhtp5.ch08; a.The statement declares a package that exists at deitel.com. b.The statement uses the Sun Microsystems convention of package naming. c.The statement specifies a package that can be imported using: import com.deitel.ch08. d.The statement will generate a compile time error. ANS: b. The statement uses the Sun Microsystems convention of package naming. Section 8.14 8.14 Q1: When no member access modifier is specified for a method or variable, the method or variable: a.Is public. b.Is private. c.Has package access. d.Is static. ANS: c. Has package access. Section 8.15 8.15 Q1: Java programmers do not focus on: a.Crafting new classes and reusing existing classes. b.Understanding class library implementations c.Carefully testing classes they design. d.Carefully documenting classes they design. ANS: b. Understanding class library implementations. Information hiding and well-defined interfaces free Java programmers from needing to understand existing class library implementations. 8.15 Q2: Which of the following does not contribute to improved software reusability? a.Quickly creating new class libraries without testing them thoroughly. b.Licensing schemes and protection mechanisms. c.Descriptions of classes that allow programmers to determine whether a class fits their needs. d.Cataloging schemes and browsing mechanisms. ANS: Quickly creating new class libraries without testing them thoroughly. Section 8.16 8.16 Q1: Abstract Data Types: a.Elevate the importance of data. b.Are only approximation or models of real-world concepts and behaviors. c.Capture tow notions, data representation and operations. d.All of the above. ANS: d. All of the above. 8.16 Q2: The term information hiding refers to: a.public methods. b.Hiding implementation details from clients of a class. c.Accessing static class members. © Copyright 2003 by Deitel & Associates, Inc. and Prentice Hall. All Rights Reserved. Java How to Program, 5/e Test Item File 5 of 5 d.The process of releasing an object for garbage collection.
Load more

Recommended publications
  • ISO/IEC JTC 1/SC 22/WG4 N 0163 Information Technology
    ISO/IEC JTC 1/SC 22/WG4 N 0163 Date: 2002-05-21 Reference number of document: WDTR 19755 Version 1.1 Committee identification: ISO/IEC JTC 1/SC 22 /WG 4 Secretariat: ANSI Information Technology — Programming languages, their environments and system software interfaces — Object finalization for programming language COBOL Warning This document is an ISO/IEC proposed draft Technical Report. It is not an ISO/IEC International Technical Report. It is distributed for review and comment. It is subject to change without notice and shall not be referred to as an International Technical Report or International Standard. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. Document type: Technical report Document subtype: n/a Document stage: (20) Preparation Document language: E ISO/WDTR 19755 Copyright notice This ISO/IEC document is a working draft and is copyright-protected by ISO/IEC. Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO’s member body in the country of the requester: Copyright manager ISO Central Secretariat 1 rue de Varembé 1211 Geneva 20 Switzerland tel: +41 22 749 0111 fax: +41 22 734 0179 email: [email protected] Reproduction for sales purposes may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. ii © ISO/IEC 2002 – All rights reserved ISO/IEC WDTR 19755 Acknowledgement notice COBOL originated in 1959 as a common business oriented language developed by the Conference on Data Systems Languages (CODASYL).
    [Show full text]
  • Stable/Build) • --Port PORT - Set the PORT Number (Default: 8000)
    Pyodide Release 0.18.1 unknown Sep 16, 2021 CONTENTS 1 Using Pyodide 3 1.1 Getting started..............................................3 1.2 Downloading and deploying Pyodide..................................6 1.3 Using Pyodide..............................................7 1.4 Loading packages............................................ 12 1.5 Type translations............................................. 14 1.6 Pyodide Python compatibility...................................... 25 1.7 API Reference.............................................. 26 1.8 Frequently Asked Questions....................................... 50 2 Development 55 2.1 Building from sources.......................................... 55 2.2 Creating a Pyodide package....................................... 57 2.3 How to Contribute............................................ 64 2.4 Testing and benchmarking........................................ 74 2.5 Interactive Debugging.......................................... 76 3 Project 79 3.1 About Pyodide.............................................. 79 3.2 Roadmap................................................. 80 3.3 Code of Conduct............................................. 82 3.4 Governance and Decision-making.................................... 83 3.5 Change Log............................................... 85 3.6 Related Projects............................................. 95 4 Indices and tables 97 Python Module Index 99 Index 101 i ii Pyodide, Release 0.18.1 Python with the scientific stack, compiled to WebAssembly.
    [Show full text]
  • Visual Smalltalk Enterprise ™ ™
    Visual Smalltalk Enterprise ™ ™ Language Reference P46-0201-00 Copyright © 1999–2000 Cincom Systems, Inc. All rights reserved. Copyright © 1999–2000 Seagull Systems, Inc. All rights reserved. This product contains copyrighted third-party software. Part Number: P46-0201-00 Software Release 3.2 This document is subject to change without notice. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Trademark acknowledgments: CINCOM, CINCOM SYSTEMS, and the Cincom logo are registered trademarks of Cincom Systems, Inc. Visual Smalltalk is a trademark of Cincom Systems, Inc., its subsidiaries, or successors and are registered in the United States and other countries. Microsoft Windows is a registered trademark of Microsoft, Inc. Win32 is a trademark of Microsoft, Inc. OS/2 is a registered trademark of IBM Corporation. Other product names mentioned herein are used for identification purposes only, and may be trademarks of their respective companies. The following copyright notices apply to software that accompanies this documentation: Visual Smalltalk is furnished under a license and may not be used, copied, disclosed, and/or distributed except in accordance with the terms of said license. No class names, hierarchies, or protocols may be copied for implementation in other systems. This manual set and online system documentation copyright © 1999–2000 by Cincom Systems, Inc. All rights reserved. No part of it may be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form without prior written consent from Cincom.
    [Show full text]
  • Gnu Smalltalk Library Reference Version 3.2.5 24 November 2017
    gnu Smalltalk Library Reference Version 3.2.5 24 November 2017 by Paolo Bonzini 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, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". 1 3 1 Base classes 1.1 Tree Classes documented in this manual are boldfaced. Autoload Object Behavior ClassDescription Class Metaclass BlockClosure Boolean False True CObject CAggregate CArray CPtr CString CCallable CCallbackDescriptor CFunctionDescriptor CCompound CStruct CUnion CScalar CChar CDouble CFloat CInt CLong CLongDouble CLongLong CShort CSmalltalk CUChar CByte CBoolean CUInt CULong CULongLong CUShort ContextPart 4 GNU Smalltalk Library Reference BlockContext MethodContext Continuation CType CPtrCType CArrayCType CScalarCType CStringCType Delay Directory DLD DumperProxy AlternativeObjectProxy NullProxy VersionableObjectProxy PluggableProxy SingletonProxy DynamicVariable Exception Error ArithmeticError ZeroDivide MessageNotUnderstood SystemExceptions.InvalidValue SystemExceptions.EmptyCollection SystemExceptions.InvalidArgument SystemExceptions.AlreadyDefined SystemExceptions.ArgumentOutOfRange SystemExceptions.IndexOutOfRange SystemExceptions.InvalidSize SystemExceptions.NotFound SystemExceptions.PackageNotAvailable SystemExceptions.InvalidProcessState SystemExceptions.InvalidState
    [Show full text]
  • A Tour of the Squeak Object Engine
    A Tour of the Squeak Object Engine A Tour of the Squeak Object Engine Tim Rowledge, [email protected] Introduction This chapter is intended to explain some basics of how a Virtual Machine (VM) works, why a VM is useful, what it does for the Squeak programmer and user, and how the Squeak VM might develop in the future. What is a Virtual Machine and why do we need one? A Virtual Machine provides us with a pretense of being a machine other than the actual hardware in use. Using one allows systems that behave differently than the host hardware to run as if on hardware designed for them. The term Object Engine is less commonly used but is a useful concept that includes the lowest system areas of the langauge environment running on the VM. Since there is often some flux in the definition of which components are within the actual VM and which are part of the supported environment, Object Engine is useful as a more inclusive term. The term Virtual Machine is used in several ways. When IBM refer to VM/CMS they are referring to a way of making a mainframe behave as if it is many machines, so that programs can assume they have total control even though they do not. Intel provide a somewhat similar facility in the x86 architecture(?), referred to as Virtual Mode. This sort of VM is a complete hardware simulation, often supported at the lowest level by the hardware. Another sort of VM is the emulator - SoftWindows for the Mac, Acorn's !PC, Linux's WINE are good examples - where another machine and/or OS is simulated to allow a Mac user to run Windows programs, an Acorn RiscPC or a Linux machine to run Windows98 programs and so on.
    [Show full text]
  • Exposing C++ Functions and Classes with Rcpp Modules
    Exposing C++ functions and classes with Rcpp modules Dirk Eddelbuettela and Romain Françoisb ahttp://dirk.eddelbuettel.com; bhttps://romain.rbind.io/ This version was compiled on July 3, 2021 This note discusses Rcpp modules. Rcpp modules allow programmers to Here we use the (templated) Rcpp converter as() which can expose C++ functions and classes to R with relative ease. Rcpp modules transform from a SEXP to a number of different C++ and Rcpp are inspired from the Boost.Python C++ library (Abrahams and Grosse- types. The Rcpp function wrap() offers the opposite functionality Kunstleve, 2003) which provides similar features for Python. and converts many known types to a SEXP. This process is simple enough, and is used by a number of Rcpp | modules | R | C++ CRAN packages. However, it requires direct involvement from the programmer, which quickly becomes tiresome when many functions 1. Motivation are involved. Rcpp modules provides a much more elegant and Exposing C++ functionality to R is greatly facilitated by the Rcpp unintrusive way to expose C++ functions such as the norm function package and its underlying C++ library (Eddelbuettel et al., 2021; shown above to R. Eddelbuettel and François, 2011). Rcpp smoothes many of the We should note that Rcpp now has Rcpp attributes which ex- rough edges in R and C++ integration by replacing the traditional tends certain aspect of Rcpp modules and makes binding to simple R Application Programming Interface (API) described in ‘Writing functions such as this one even easier. With Rcpp attributes we can R Extensions’(R Core Team, 2018) with a consistent set of C++ just write classes.
    [Show full text]
  • FFI: Racket Foreign Interface
    FFI: Racket Foreign Interface Version 5.0 Eli Barzilay June 6, 2010 (require ffi/unsafe) The ffi/unsafe library enables the direct use of C-based APIs within Racket programs— without writing any new C code. From the Racket perspective, functions and data with a C-based API are foreign, hence the term foreign interface. Furthermore, since most APIs consist mostly of functions, the foreign interface is sometimes called a foreign function in- terface, abbreviated FFI. 1 Contents 1 Overview 4 2 Loading Foreign Libraries 5 3 C Types 8 3.1 Type Constructors . 8 3.2 Numeric Types . 9 3.3 Other Atomic Types . 10 3.4 String Types . 11 3.4.1 Primitive String Types . 11 3.4.2 Fixed Auto-Converting String Types . 11 3.4.3 Variable Auto-Converting String Type . 12 3.4.4 Other String Types . 12 3.5 Pointer Types . 13 3.6 Function Types . 14 3.6.1 Custom Function Types . 18 3.7 C Struct Types . 21 3.8 Enumerations and Masks . 24 4 Pointer Functions 26 4.1 Pointer Dereferencing . 27 4.2 Memory Management . 30 5 Derived Utilities 34 5.1 Safe Homogenous Vectors . 34 5.2 Safe C Vectors . 40 2 5.3 Tagged C Pointer Types . 42 5.4 Defining Bindings . 44 5.5 Allocation and Finalization . 46 5.6 Atomic Execution . 47 5.7 Objective-C FFI . 48 5.7.1 FFI Types and Constants . 48 5.7.2 Syntactic Forms and Procedures . 49 5.7.3 Raw Runtime Functions . 53 5.7.4 Legacy Library .
    [Show full text]
  • Running Android Applications Without a Virtual Machine
    Running Android Applications without a Virtual Machine Arno Puder San Francisco State University Computer Science Department 1600 Holloway Avenue San Francisco, CA 94132 [email protected] Abstract. Android has gained significant popularity in the smartphone market since its introduction in 2007. While Android applications are written in Java, Android uses its own virtual machine called Dalvik. Other smartphone platforms, most notably Apple’s iOS, do not permit the installation of any kind of virtual machine. App developers who want to publish their applications for different platforms are required to re- implement the application using the respective native SDK. In this paper we describe a cross-compilation approach, whereby Android applications are cross-compiled to portable C code. With this approach it is not nec- essary to have a Dalvik virtual machine deployed on the target platform. We describe different aspects of our cross-compiler, from byte code level cross-compilation, memory management, to API mapping. A prototype of our cross-compiler called XMLVM is available under an Open Source license. 1 Introduction Android is a software stack for mobile devices initially developed by a company called Android, Inc. before being bought by Google in 2005. Since 2007, mem- bers of the Open Handset Alliance (OHA) collaborate on the development of Android which nowadays has become one of the main development platforms for smartphone applications. Although Android employs Java as a programming language as well as a subset of the standard J2SE API, it does not make use of Oracle’s (formerly Sun Microsystem’s) virtual machine technology for technical and political reasons.
    [Show full text]
  • Diagnostic Data Collection and Analysis Tools
    Lesson 3 Diagnostic Data Collection and Analysis tools Poonam Parhar JVM Sustaining Engineer Oracle Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | Agenda Diagnostic Data, Data Collection and Analysis tools 1. Java Heap Memory Issues 2. OutOfMemoryError due to Finalization 3. PermGen/Metaspace Memory Issues 4. CodeCache Issues 5. Native Memory Issues Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | 3 Java Heap: Memory Leak Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | 4 Confirm Memory Leak • Monitor Java Heap usage over time • If the Full GCs are not able to claim any space in the Old Gen of the heap then it could be a configuration issue • Heap might be sized too small • Increase the heap size and test the application again • If there is continuous memory growth and the failure persists at the increased heap size too, there could be a memory leak Copyright © 2017, Oracle and/or its affiliates. All rights reserved. | 5 Monitor using GC Logs [GC (Allocation Failure) [PSYoungGen: 318596K->153251K(433152K)] 1184491K->1182018K(1556992K), 0.5548358 secs] [Times: user=1.78 sys=0.13, real=0.56 secs] [Full GC (Ergonomics) [PSYoungGen: 153251K->0K(433152K)] [ParOldGen: 1028766K->1054946K(1345024K)] 1182018K->1054946K(1778176K), [Metaspace: 2722K->2722K(1056768K)], 4.5281743 secs] [Times: user=10.09 sys=0.00, real=4.52 secs] [GC (Allocation Failure) [PSYoungGen: 209408K->209511K(448512K)] 1264354K->1264458K(1793536K), 0.1590964 secs] [Times: user=0.48 sys=0.06, real=0.15 secs]
    [Show full text]
  • Extensible Virtual Machines
    UCAM-CL-TR-525 Technical Report ISSN 1476-2986 Number 525 Computer Laboratory Extensible virtual machines Timothy L. Harris December 2001 JJ Thomson Avenue Cambridge CB3 0FD United Kingdom phone +44 1223 763500 http://www.cl.cam.ac.uk/ c 2001 Timothy L. Harris This technical report is based on a dissertation submitted by the author for the degree of Doctor of Philosophy to the University of Cambridge. Technical reports published by the University of Cambridge Computer Laboratory are freely available via the Internet: http://www.cl.cam.ac.uk/TechReports/ Series editor: Markus Kuhn ISSN 1476-2986 Abstract Virtual machines (vms) have enjoyed a resurgence as a way of allowing the same application program to be used across a range of computer systems. This flexibility comes from the abstraction that the vm provides over the native interface of a particular computer. However, this also means that the application is prevented from taking the features of particular physical machines into account in its implementation. This dissertation addresses the question of why, where and how it is useful, possible and practicable to provide an application with access to lower-level interfaces. It argues that many aspects of vm implementation can be devolved safely to untrusted applications and demonstrates this through a prototype which allows control over run-time compilation, object placement within the heap and thread scheduling. The proposed architecture separates these application-specific policy implementations from the application itself. This allows one application to be used with different policies on different systems and also allows naïve or premature optimizations to be removed.
    [Show full text]
  • Iso/Iec Tr 19755:2003(E)
    This is a preview - click here to buy the full publication TECHNICAL ISO/IEC REPORT TR 19755 First edition 2003-12-01 Information technology — Programming languages, their environments and system software interfaces — Object finalization for programming language COBOL Technologies de l'information — Langages de programmation, leurs environnements et interfaces logiciel système — Finalisation d'objet pour le langage de programmation COBOL Reference number ISO/IEC TR 19755:2003(E) © ISO/IEC 2003 ISO/IEC TR 19755:2003(E) This is a preview - click here to buy the full publication PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below. © ISO/IEC 2003 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.
    [Show full text]
  • Memory Management in the D Programming Language
    Technical University of Moldova MEMORY MANAGEMENT IN THE D PROGRAMMING LANGUAGE Student: Panteleev Vladimir Advisor: Lect. Sup. Melnic Radu Chişinău – 2009 Ministerul Educaţiei şi Tineretului al Republicii Moldova Universitatea Tehnică a Moldovei Facultatea de Calculatoare, Informatică şi Microelectronică Catedra Filiera Anglofonă Admis la susţinere Şef de catedră: conf. unif. dr. Bostan Viorel _____________________________ „__”_____________ 200_ Memory Management in the D Programming Language Proiect de licenţă Student: _______________ (Panteleev V. ) Conducător: ____________ (Melnic R. ___ ) Consultanţi: ____________ (Bostan V. ___ ) _____________ (Nicolenco V. ) _____________ (Guţu Al. ____ ) Chişinău – 2009 Abstract This report describes a study of automatic memory management techniques, their implementation in the D Programming Language, and work to improve the state of memory management in the D Programming Language. Chapter 1 describes garbage collection as a form of automatic memory management. Automatic memory management implies freeing the programmer of the task of manually managing system memory. This approach has several advantages, such as less programming effort, as well as some disadvantages. Chapter 2 outlines the D programming language. D is based on C/C++, however it breaks backwards compatibility in favor of redesigned features, as well as introducing new features present in other modern languages. One of these features is automatic memory management using garbage collection, which is also described in detail. Chapter 3 contains three problems commonly encountered while authoring programs in the D programming language (and possibly other garbage collected languages). The covered problems are inadequate performance, memory corruption and memory leaks. The problems are analyzed, and appropriate solutions are developed and deployed. Chapter 4 introduces Diamond, a memory debugger and profiler developed specifically for the D programming language.
    [Show full text]