DOCSLIB.ORG

SBCL User Manual SBCL Version 2.1.9 2021-09 This Manual Is Part of the SBCL Software System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SBCL User Manual SBCL Version 2.1.9 2021-09 This Manual Is Part of the SBCL Software System SBCL User Manual SBCL version 2.1.9 2021-09 This manual is part of the SBCL software system. See the README file for more information. This manual is largely derived from the manual for the CMUCL system, which was produced at Carnegie Mellon University and later released into the public domain. This manual is in the public domain and is provided with absolutely no warranty. See the COPYING and CREDITS files for more information. i Table of Contents 1 Getting Support and Reporting Bugs ::::::::::::::::::::::::::::::::::::::::: 1 1.1 Volunteer Support ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Commercial Support::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.3 Reporting Bugs:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.3.1 How to Report Bugs Effectively::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.3.2 Signal Related Bugs :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2 Introduction ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.1 ANSI Conformance :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.1.1 Exceptions ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.2 Extensions::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.3 Idiosyncrasies:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2.3.1 Declarations :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2.3.2 FASL Format::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2.3.3 Compiler-only Implementation :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.3.4 Defining Constants ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.3.5 Style Warnings ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.4 Development Tools :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.4.1 Editor Integration :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.4.2 Language Reference :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.4.3 Generating Executables::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.5 More SBCL Information ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.5.1 SBCL Homepage ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.5.2 Online Documentation:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.5.3 Additional Documentation Files :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.5.4 Internals Documentation:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.6 More Common Lisp Information ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.6.1 Internet Community :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.6.2 Third-party Libraries ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.6.3 Common Lisp Books ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.7 History and Implementation of SBCL :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 3 Starting and Stopping :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 3.1 Starting SBCL::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 3.1.1 From Shell to Lisp:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 3.1.2 Running from Emacs ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 3.1.3 Shebang Scripts :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 3.2 Stopping SBCL :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 3.2.1 Exit :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 3.2.2 End of File :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 10 3.2.3 Saving a Core Image :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 10 3.2.4 Exit on Errors::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 3.3 Command Line Options :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 3.3.1 Runtime Options :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 3.3.2 Toplevel Options :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 3.4 Initialization Files :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 14 3.5 Initialization and Exit Hooks ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 14 4 Compiler :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 15 4.1 Diagnostic Messages :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 15 4.1.1 Controlling Verbosity :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 15 4.1.2 Diagnostic Severity :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 16 ii 4.1.3 Understanding Compile Diagnostics:::::::::::::::::::::::::::::::::::::::::::::::::::::: 16 4.1.3.1 The Parts of a Compiler Diagnostic::::::::::::::::::::::::::::::::::::::::::::::::: 16 4.1.3.2 The Original and Actual Source :::::::::::::::::::::::::::::::::::::::::::::::::::: 18 4.1.3.3 The Processing Path ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 18 4.2 Handling of Types :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 19 4.2.1 Declarations as Assertions ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 19 4.2.2 Precise Type Checking :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 19 4.2.3 Getting Existing Programs to Run::::::::::::::::::::::::::::::::::::::::::::::::::::::: 20 4.2.4 Implementation Limitations ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 21 4.3 Compiler Policy :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 21 4.4 Compiler Errors :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 23 4.4.1 Type Errors at Compile Time ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 23 4.4.2 Errors During Macroexpansion :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 24 4.4.3 Read Errors ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 24 4.5 Open Coding and Inline Expansion ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 24 4.6 Interpreter ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 25 4.7 Advanced Compiler Use and Efficiency Hints:::::::::::::::::::::::::::::::::::::::::::::::::: 25 5 Debugger ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 26 5.1 Debugger Entry :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 26 5.1.1 Debugger Banner:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 26 5.1.2 Debugger Invocation :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 26 5.2 Debugger Command Loop :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 26 5.3 Stack Frames ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 27 5.3.1 Stack Motion:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 27 5.3.2 How Arguments are Printed ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 27 5.3.3 Function Names ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 28 5.3.3.1 Entry Point Details :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 28 5.3.4 Debug Tail Recursion:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 28 5.3.5 Unknown Locations and Interrupts :::::::::::::::::::::::::::::::::::::::::::::::::::::: 29 5.4 Variable Access::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 29 5.4.1 Variable Value Availability :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 30 5.4.2 Note On Lexical Variable Access::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 30 5.5 Source Location Printing ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 31 5.5.1 How the Source is Found :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 31 5.5.2 Source Location Availability ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 32 5.6 Debugger Policy Control:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 32 5.7 Exiting Commands ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 33 5.8 Information Commands::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 33 5.9 Function Tracing ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 34 5.10 Single Stepping:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 35 5.11 Enabling and Disabling the Debugger :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 36 6 Efficiency ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 37 6.1 Slot access ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 37 6.1.1 Structure object slot access ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Load more

Recommended publications
  • Technical Standard
    Technical Standard X/Open Curses, Issue 7 The Open Group ©November 2009, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. Technical Standard X/Open Curses, Issue 7 ISBN: 1-931624-83-6 Document Number: C094 Published in the U.K. by The Open Group, November 2009. This standardhas been prepared by The Open Group Base Working Group. Feedback relating to the material contained within this standardmay be submitted by using the web site at http://austingroupbugs.net with the Project field set to "Xcurses Issue 7". ii Technical Standard 2009 Contents Chapter 1 Introduction........................................................................................... 1 1.1 This Document ........................................................................................ 1 1.1.1 Relationship to Previous Issues ......................................................... 1 1.1.2 Features Introduced in Issue 7 ........................................................... 2 1.1.3 Features Withdrawn in Issue 7........................................................... 2 1.1.4 Features Introduced in Issue 4 ........................................................... 2 1.2 Conformance............................................................................................ 3 1.2.1 Base Curses Conformance .................................................................
    [Show full text]
  • The Clon User Manual the Command-Line Options Nuker, Version 1.0 Beta 25 "Michael Brecker"
    The Clon User Manual The Command-Line Options Nuker, Version 1.0 beta 25 "Michael Brecker" Didier Verna <[email protected]> Copyright c 2010{2012, 2015, 2017, 2020, 2021 Didier Verna Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the section entitled \Copy- ing" is included exactly as in the original. Permission is granted to copy and distribute translations of this manual into an- other language, under the above conditions for modified versions, except that this permission notice may be translated as well. Cover art by Alexis Angelidis. i Table of Contents Copying ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1 Introduction :::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2 Installation:::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 3 Quick Start ::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 3.1 Full Source :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 3.2 Explanation ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 4 Using Clon :::::::::::::::::::::::::::::::::::::::::::::::::::: 11 4.1 Synopsis Definition ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 11 4.1.1 Synopsis Items ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 11 4.1.1.1 Text ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Modern Programming Languages CS508 Virtual University of Pakistan
    Modern Programming Languages (CS508) VU Modern Programming Languages CS508 Virtual University of Pakistan Leaders in Education Technology 1 © Copyright Virtual University of Pakistan Modern Programming Languages (CS508) VU TABLE of CONTENTS Course Objectives...........................................................................................................................4 Introduction and Historical Background (Lecture 1-8)..............................................................5 Language Evaluation Criterion.....................................................................................................6 Language Evaluation Criterion...................................................................................................15 An Introduction to SNOBOL (Lecture 9-12).............................................................................32 Ada Programming Language: An Introduction (Lecture 13-17).............................................45 LISP Programming Language: An Introduction (Lecture 18-21)...........................................63 PROLOG - Programming in Logic (Lecture 22-26) .................................................................77 Java Programming Language (Lecture 27-30)..........................................................................92 C# Programming Language (Lecture 31-34) ...........................................................................111 PHP – Personal Home Page PHP: Hypertext Preprocessor (Lecture 35-37)........................129 Modern Programming Languages-JavaScript
    [Show full text]
  • An Implementation of Python for Racket
    An Implementation of Python for Racket Pedro Palma Ramos António Menezes Leitão INESC-ID, Instituto Superior Técnico, INESC-ID, Instituto Superior Técnico, Universidade de Lisboa Universidade de Lisboa Rua Alves Redol 9 Rua Alves Redol 9 Lisboa, Portugal Lisboa, Portugal [email protected] [email protected] ABSTRACT Keywords Racket is a descendent of Scheme that is widely used as a Python; Racket; Language implementations; Compilers first language for teaching computer science. To this end, Racket provides DrRacket, a simple but pedagogic IDE. On the other hand, Python is becoming increasingly popular 1. INTRODUCTION in a variety of areas, most notably among novice program- The Racket programming language is a descendent of Scheme, mers. This paper presents an implementation of Python a language that is well-known for its use in introductory for Racket which allows programmers to use DrRacket with programming courses. Racket comes with DrRacket, a ped- Python code, as well as adding Python support for other Dr- agogic IDE [2], used in many schools around the world, as Racket based tools. Our implementation also allows Racket it provides a simple and straightforward interface aimed at programs to take advantage of Python libraries, thus signif- inexperienced programmers. Racket provides different lan- icantly enlarging the number of usable libraries in Racket. guage levels, each one supporting more advanced features, that are used in different phases of the courses, allowing Our proposed solution involves compiling Python code into students to benefit from a smoother learning curve. Fur- semantically equivalent Racket source code. For the run- thermore, Racket and DrRacket support the development of time implementation, we present two different strategies: additional programming languages [13].
    [Show full text]
  • About ILE C/C++ Compiler Reference
    IBM i 7.3 Programming IBM Rational Development Studio for i ILE C/C++ Compiler Reference IBM SC09-4816-07 Note Before using this information and the product it supports, read the information in “Notices” on page 121. This edition applies to IBM® Rational® Development Studio for i (product number 5770-WDS) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CISC models. This document may contain references to Licensed Internal Code. Licensed Internal Code is Machine Code and is licensed to you under the terms of the IBM License Agreement for Machine Code. © Copyright International Business Machines Corporation 1993, 2015. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents ILE C/C++ Compiler Reference............................................................................... 1 What is new for IBM i 7.3.............................................................................................................................3 PDF file for ILE C/C++ Compiler Reference.................................................................................................5 About ILE C/C++ Compiler Reference......................................................................................................... 7 Prerequisite and Related Information..................................................................................................
    [Show full text]
  • The Machine That Builds Itself: How the Strengths of Lisp Family
    Khomtchouk et al. OPINION NOTE The Machine that Builds Itself: How the Strengths of Lisp Family Languages Facilitate Building Complex and Flexible Bioinformatic Models Bohdan B. Khomtchouk1*, Edmund Weitz2 and Claes Wahlestedt1 *Correspondence: [email protected] Abstract 1Center for Therapeutic Innovation and Department of We address the need for expanding the presence of the Lisp family of Psychiatry and Behavioral programming languages in bioinformatics and computational biology research. Sciences, University of Miami Languages of this family, like Common Lisp, Scheme, or Clojure, facilitate the Miller School of Medicine, 1120 NW 14th ST, Miami, FL, USA creation of powerful and flexible software models that are required for complex 33136 and rapidly evolving domains like biology. We will point out several important key Full list of author information is features that distinguish languages of the Lisp family from other programming available at the end of the article languages and we will explain how these features can aid researchers in becoming more productive and creating better code. We will also show how these features make these languages ideal tools for artificial intelligence and machine learning applications. We will specifically stress the advantages of domain-specific languages (DSL): languages which are specialized to a particular area and thus not only facilitate easier research problem formulation, but also aid in the establishment of standards and best programming practices as applied to the specific research field at hand. DSLs are particularly easy to build in Common Lisp, the most comprehensive Lisp dialect, which is commonly referred to as the “programmable programming language.” We are convinced that Lisp grants programmers unprecedented power to build increasingly sophisticated artificial intelligence systems that may ultimately transform machine learning and AI research in bioinformatics and computational biology.
    [Show full text]
  • Bringing GNU Emacs to Native Code
    Bringing GNU Emacs to Native Code Andrea Corallo Luca Nassi Nicola Manca [email protected] [email protected] [email protected] CNR-SPIN Genoa, Italy ABSTRACT such a long-standing project. Although this makes it didactic, some Emacs Lisp (Elisp) is the Lisp dialect used by the Emacs text editor limitations prevent the current implementation of Emacs Lisp to family. GNU Emacs can currently execute Elisp code either inter- be appealing for broader use. In this context, performance issues preted or byte-interpreted after it has been compiled to byte-code. represent the main bottleneck, which can be broken down in three In this work we discuss the implementation of an optimizing com- main sub-problems: piler approach for Elisp targeting native code. The native compiler • lack of true multi-threading support, employs the byte-compiler’s internal representation as input and • garbage collection speed, exploits libgccjit to achieve code generation using the GNU Com- • code execution speed. piler Collection (GCC) infrastructure. Generated executables are From now on we will focus on the last of these issues, which con- stored as binary files and can be loaded and unloaded dynamically. stitutes the topic of this work. Most of the functionality of the compiler is written in Elisp itself, The current implementation traditionally approaches the prob- including several optimization passes, paired with a C back-end lem of code execution speed in two ways: to interface with the GNU Emacs core and libgccjit. Though still a work in progress, our implementation is able to bootstrap a func- • Implementing a large number of performance-sensitive prim- tional Emacs and compile all lexically scoped Elisp files, including itive functions (also known as subr) in C.
    [Show full text]
  • Technical Study Desktop Internationalization
    Technical Study Desktop Internationalization NIC CH A E L T S T U D Y [This page intentionally left blank] X/Open Technical Study Desktop Internationalisation X/Open Company Ltd. December 1995, X/Open Company Limited All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners. X/Open Technical Study Desktop Internationalisation X/Open Document Number: E501 Published by X/Open Company Ltd., U.K. Any comments relating to the material contained in this document may be submitted to X/Open at: X/Open Company Limited Apex Plaza Forbury Road Reading Berkshire, RG1 1AX United Kingdom or by Electronic Mail to: [email protected] ii X/Open Technical Study (1995) Contents Chapter 1 Internationalisation.............................................................................. 1 1.1 Introduction ................................................................................................. 1 1.2 Character Sets and Encodings.................................................................. 2 1.3 The C Programming Language................................................................ 5 1.4 Internationalisation Support in POSIX .................................................. 6 1.5 Internationalisation Support in the X/Open CAE............................... 7 1.5.1 XPG4 Facilities.........................................................................................
    [Show full text]
  • Common Lispworks User Guide
    LispWorks® for the Windows® Operating System Common LispWorks User Guide Version 5.1 Copyright and Trademarks Common LispWorks User Guide (Windows version) Version 5.1 February 2008 Copyright © 2008 by LispWorks Ltd. All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of LispWorks Ltd. The information in this publication is provided for information only, is subject to change without notice, and should not be construed as a commitment by LispWorks Ltd. LispWorks Ltd assumes no responsibility or liability for any errors or inaccuracies that may appear in this publication. The software described in this book is furnished under license and may only be used or copied in accordance with the terms of that license. LispWorks and KnowledgeWorks are registered trademarks of LispWorks Ltd. Adobe and PostScript are registered trademarks of Adobe Systems Incorporated. Other brand or product names are the registered trade- marks or trademarks of their respective holders. The code for walker.lisp and compute-combination-points is excerpted with permission from PCL, Copyright © 1985, 1986, 1987, 1988 Xerox Corporation. The XP Pretty Printer bears the following copyright notice, which applies to the parts of LispWorks derived therefrom: Copyright © 1989 by the Massachusetts Institute of Technology, Cambridge, Massachusetts. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, pro- vided that this copyright and permission notice appear in all copies and supporting documentation, and that the name of M.I.T.
    [Show full text]
  • IDE User Guide Version 7.1 Copyright and Trademarks Lispworks IDE User Guide (Unix Version) Version 7.1 September 2017 Copyright © 2017 by Lispworks Ltd
    LispWorks® IDE User Guide Version 7.1 Copyright and Trademarks LispWorks IDE User Guide (Unix version) Version 7.1 September 2017 Copyright © 2017 by LispWorks Ltd. All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of LispWorks Ltd. The information in this publication is provided for information only, is subject to change without notice, and should not be construed as a commitment by LispWorks Ltd. LispWorks Ltd assumes no responsibility or liability for any errors or inaccuracies that may appear in this publication. The software described in this book is furnished under license and may only be used or copied in accordance with the terms of that license. LispWorks and KnowledgeWorks are registered trademarks of LispWorks Ltd. Adobe and PostScript are registered trademarks of Adobe Systems Incorporated. Other brand or product names are the registered trade- marks or trademarks of their respective holders. The code for walker.lisp and compute-combination-points is excerpted with permission from PCL, Copyright © 1985, 1986, 1987, 1988 Xerox Corporation. The XP Pretty Printer bears the following copyright notice, which applies to the parts of LispWorks derived therefrom: Copyright © 1989 by the Massachusetts Institute of Technology, Cambridge, Massachusetts. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, pro- vided that this copyright and permission notice appear in all copies and supporting documentation, and that the name of M.I.T.
    [Show full text]
  • Omnipresent and Low-Overhead Application Debugging
    Omnipresent and low-overhead application debugging Robert Strandh [email protected] LaBRI, University of Bordeaux Talence, France ABSTRACT application programmers as opposed to system programmers. The state of the art in application debugging in free Common The difference, in the context of this paper, is that the tech- Lisp implementations leaves much to be desired. In many niques that we suggest are not adapted to debugging the cases, only a backtrace inspector is provided, allowing the system itself, such as the compiler. Instead, throughout this application programmer to examine the control stack when paper, we assume that, as far as the application programmer an unhandled error is signaled. Most such implementations do is concerned, the semantics of the code generated by the not allow the programmer to set breakpoints (unconditional compiler corresponds to that of the source code. or conditional), nor to step the program after it has stopped. In this paper, we are mainly concerned with Common Furthermore, even debugging tools such as tracing or man- Lisp [1] implementations distributed as so-called FLOSS, i.e., ually calling break are typically very limited in that they do \Free, Libre, and Open Source Software". While some such not allow the programmer to trace or break in important sys- implementations are excellent in terms of the quality of the tem functions such as make-instance or shared-initialize, code that the compiler generates, most leave much to be simply because these tools impact all callers, including those desired when it comes to debugging tools available to the of the system itself, such as the compiler.
    [Show full text]
  • How Lisp Systems Look Different in Proceedings of European Conference on Software Maintenance and Reengineering (CSMR 2008)
    How Lisp Systems Look Different In Proceedings of European Conference on Software Maintenance and Reengineering (CSMR 2008) Adrian Dozsa Tudor Gˆırba Radu Marinescu Politehnica University of Timis¸oara University of Berne Politehnica University of Timis¸oara Romania Switzerland Romania [email protected] [email protected] [email protected] Abstract rently used in a variety of domains, like bio-informatics (BioBike), data mining (PEPITe), knowledge-based en- Many reverse engineering approaches have been devel- gineering (Cycorp or Genworks), video games (Naughty oped to analyze software systems written in different lan- Dog), flight scheduling (ITA Software), natural language guages like C/C++ or Java. These approaches typically processing (SRI International), CAD (ICAD or OneSpace), rely on a meta-model, that is either specific for the language financial applications (American Express), web program- at hand or language independent (e.g. UML). However, one ming (Yahoo! Store or reddit.com), telecom (AT&T, British language that was hardly addressed is Lisp. While at first Telecom Labs or France Telecom R&D), electronic design sight it can be accommodated by current language inde- automation (AMD or American Microsystems) or planning pendent meta-models, Lisp has some unique features (e.g. systems (NASA’s Mars Pathfinder spacecraft mission) [16]. macros, CLOS entities) that are crucial for reverse engi- neering Lisp systems. In this paper we propose a suite of Why Lisp is Different. In spite of its almost fifty-year new visualizations that reveal the special traits of the Lisp history, and of the fact that other programming languages language and thus help in understanding complex Lisp sys- borrowed concepts from it, Lisp still presents some unique tems.
    [Show full text]