DOCSLIB.ORG

Allegro CL 3.0 for Windows Printed Documentation in PDF Format

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Allegro CL 3.0 for Windows Printed Documentation in PDF Format Glossary Allegro CL 3.0 for Windows printed documentation in PDF format All the printed documentation for Allegro CL 3.0 for Windows is available in this pdf file and is readable with an Adobe Acrobat Reader. Please Note: • There are links in each Table of Contents page. Clicking on a chapter or section (but not heading) title causes a jump to the associated page. • There are no links in any index in this edition. • Many pictures do not appear. An apparent incompatibility in the picture format results in their not appearing in the PDF file (you see blank space instead) • If you choose ‘Bookmarks and Page’ from the View menu, you will see bookmarks for each chapter of each manual. Clicking on a bookmark will cause the associated page to be displayed (usually, the first page of the chapter). • The pagination (<chapter>-<number>) used in the printed documents does not correspond to the pagination used in the pdf file (where all pages are numbered in order from the beginning). To find a page listed PT-2-2, go to the beginning of Chapter 2 in the Programming Tools manual (using the Acrobat Bookmarks). Go to page 2 of that chapter. Copyright and Conditions of Use Copyright 1996, Franz Inc. All Rights Reserved. The PDF hypertext markup that implements the hypertext features of the Allegro CL 3.0.1 for Windows User Guide pages collectively the User Guide, is the property of Franz Inc. Distribution of the User Guide as a hypertext PDF document on the Internet does not constitute consent to any use of the underlying hypertext PDF markup for redistribution of any kind, commercial or otherwise, either via the Internet or using some other form of dis- tribution, in hypertext or otherwise. Permission to copy, distribute, display, and transmit the User Guide is granted provided that copies are not made or distributed or displayed or transmitted for direct commercial ALLEGRO CL for Windows advantage, that notice is given that copying, distribution, display, and/or transmission is by permission of Franz Inc., and that any copy made is COMPLETE and UNMODIFIED, including this copyright notice and its date. Permissions related to performance and to creation of derivative works are expressly NOT granted. Permission to make partial copies is expressly NOT granted, EXCEPT that limited per- mission is granted to transmit and display a partial copy of the User Guide for the ordinary purpose of direct viewing by a human being in the usual manner that PDF browsers permit the viewing of such a complete document, provided that no recopying, redistribution, redis- play, or retransmission is made of any such partial copy. Permission to make modified copies is expressly NOT granted. Permission to add or replace any links or any graphical images to any of these pages is expressly NOT granted. Permission to use any of the included graphical (GIF) images in any document other than the User Guide is expressly NOT granted. Restricted Rights Legend Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in (i) FAR 52.227-14 Alt III, (ii) FAR 52.227-19, (iii) DFARS 252.7013(c)(1)(ii), or (iv) the accompanying license Agreement, as applicable. For purposes of the FAR, the Software shall be deemed to be ``unpublished'' and licensed with disclosure prohibitions, rights reserved under the copyright laws of the United States. Franz Inc., 1995 University Ave., Berkeley, CA 94704.' Warranty disclaimer THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. IN NO EVENT WILL FRANZ INC. BE LIABLE FOR DIRECT, INDIRECT, SPE- CIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES RESULTING FROM ANY INACCURACY OR ERROR IN THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ALLEGRO CL for Windows Glossary PREFACE There are two volumes of bound documentation for Allegro CL for Windows. This is vol- ume 1. Each volume contains several manuals. There is also a Read This First document, which not bound in with the rest of the documentation. Here is a brief description of the documentation: 1. Read This First. This document is supplied loose. It contains information that was not put in the bound documentation. Volume 1 2. Getting Started. This document describes how to install Allegro CL for Windows on your system and it gives information about running the product. 3. Common Lisp Introduction. This document is an introduction to the Common Lisp language and the Allegro CL for Windows implementation of it. 4. Interface Builder. The Interface Builder allows you to build an interface to your application interactively. It is described in this manual. 5. Foreign Function Interface. Allegro CL for Windows supports calling applications written in languages other than Lisp. This document describes the interface. Volume 2 6. Programming Tools. This document describes the user interface to Allegro CL for Windows. In particular, it describes the Toploop window, the editor, the debugging facilities, etc. 7. General Index. An index to all documents in Volumes 1 and 2. Professional version only The Professional version of Allegro CL provides the facility to create standalone applica- tions. User who purchase the Professional version also receive the following document: Professional supplement. This document describes features available in the Pro- fessional version (but not in the standard version), including how to create stan- dalone applications. ALLEGRO CL for Windows Each individual manual has a table of contents at the beginning and an index at the end. The General Index manual, in volume 3, is an index for all manuals in Volumes 1 and 2. ALLEGRO CL for Windows Allegro CL for Windows Debugge Getting Started version 3.0 October, 1995 Copyright and other notices: This is revision 0 of this manual. This manual has Franz Inc. document number D-U-00- PC0-03-51017-3-0. Copyright 1992-1995 by Franz Inc. 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, by photocopying or recording, or otherwise, without the prior and explicit written permission of Franz incorporated. Restricted rights legend: Use, duplication, and disclosure by the United States Government are subject to Restricted Rights for Commercial Software developed at private expense as specified in DOD FAR 52.227-7013 (c) (1) (ii). Allegro CL is a registered trademarks of Franz Inc. Allegro CL for Windows is a trademark of Franz Inc. Windows, Windows 95, MS Windows, MS-DOS, and DOS are trademarks of Microsoft. Franz Inc. 1995 University Avenue Berkeley, CA 94704 U.S.A. Contents 1 Introduction 1 2 Installation 2 Installing Win32s (Windows 3.1 or Windows for Workgroups users only) 2 Allegro CL 3.0 for Windows installation 3 Reinstallation 4 Uninstall Program 5 Filename length restriction (Windows 3.1 only) 5 Debugge Professional and standard versions 5 3 Documentation 6 Volume 1 6 Volume 2 6 Professional supplement (Professional version only) 7 The Online Manual 7 Other documents for starting out 8 Pictures in the documentation 8 Change bars 9 4 When Allegro CL starts up 10 5 Features of Microsoft Windows 12 A window 12 Menus 13 Keyboard equivalents to menu items 13 Interrupting 14 What to do if the system hangs 14 The two Enter keys 15 Dialog boxes 15 ALLEGRO CL for Windows: Getting Started c - 1 6 Getting information and patches 16 The World Wide Web page 16 What is a patch 16 Getting patches 16 Where to put patch files 17 When patches are loaded 17 Creating an image with patches loaded 17 How do you know what patches are loaded in an image 18 What if a patch needs to be updated? 18 7 Example files 20 Where examples are located 20 8 Anomalies and things to note 23 Professional and standard versions are incompatible! 25 Version 2.0 fsl and img files cannot be used by version 3.0 25 Do not use 2.0 patches including FAQ patches 25 9 Support 26 Index 27 c - 2 ALLEGRO CL for Windows: Getting Started 1 Introduction Welcome to Allegro CL for Windows. This is the introductory document which will get you started with the system and direct you to the other documents and help facilities which describe how to use it. This manual is divided into the following sections: 1. Introduction. The section you are now reading. 2. Installation. This section describes how to install Allegro CL for Windows. 3. Documentation. This sections describes the documentation for Allegro CL for Debugge Windows. This section contains a description of the notation used in Allegro CL for Windows documentation. 4. When Allegro CL starts up. This section briefly describes the features on the screen and refers you to more complete documentation. 5. Features of the Microsoft Windows. Allegro CL for Windows is designed to run under various versions of the Microsoft Windows. In this section we discuss which versions and we mention certain features of MS Windows that help you when running Allegro CL for Windows. 6. Sources of information and patches. Franz Inc. maintains a World Wide Web page from which a product FAQ, patches, and other useful things can obtained. Its URL and other sources of information are described in this section. 7. Example files. A number of example files are included with the Allegro CL for Windows distribution. These are described in this section. 8. Anomalies and things to note. This section describes behavior of Allegro CL for Windows which may be unexpected or unusual.
Load more

Recommended publications
  • Educational Directory, 1
    DEPARTMENT OF THEINTERIOR BUREAU OF EDUCATION BULLETIN, 1922, No.50, EDUCATIONALDIRECTORY 1922-1923 WASHINGTON GOVERNMENT PRINTING OFFICE 1923 A u ADDITIONAL COPIES OP THIS PUBLICATION MAY BE PROCURED rams THE SUPERINTENDENT OF DOCUMENTS GOVERNMENT PRINTING OFFICE WASHINGTON, AT 115 CENTS PER COPY PURCHASER AGREES NOT TO RESELL 1SR DISTRIBUTE THIS COPT TOR PROT1T.-P1111. RES. S7, APPROVED MAY 11, 1923 IL CONTENTS. I. The United StatesBureau of Education Page: II. Principal State school officers 1 III. County and other local 3 superintendents of schools.- 13 IV. Superintendents of prIblic schools in cities and towns. 46 V. Presidents of universities andcolleges VI. Presidents of junior 67 77 VII. Heads 9f departm nts ofeducation 78 N111 I. Presidentsor deans of schools of theology 87 IX. Presidents or deans of schools of law 90 X. Presidents or deans of schools of tiielicine 92 XI. Presidents or deans of schools of dentistry 94 Presidents or deans of schools of pharmacy.. XII I. Presidents of schools of 94' osteopathy 96 X IV. Presidents or deans of srliools of veterinary medicine 96 XV. Presidents, etc.. of institutionsfor the training of teachers: 1. Presidents of teachers' colleges. 96 II. Principals of normal training schools: 1. Public normal sclu 99 2. Private normal selfols 104 'III. Directors of kindergarten training incolleges, normal schools, and kindergarten training 84110eild 105 XVI. Directors of.summer schools 109 XVII. Librarians of Public and society Librai 126 XVIII. Executive officers of State library 151 X IX. Directors of librafy schools 152 X X. Educational boards and foundations X X I. Church. educational boards and 152 societies.
    [Show full text]
  • Introduction to Programming in Lisp
    Introduction to Programming in Lisp Supplementary handout for 4th Year AI lectures · D W Murray · Hilary 1991 1 Background There are two widely used languages for AI, viz. Lisp and Prolog. The latter is the language for Logic Programming, but much of the remainder of the work is programmed in Lisp. Lisp is the general language for AI because it allows us to manipulate symbols and ideas in a commonsense manner. Lisp is an acronym for List Processing, a reference to the basic syntax of the language and aim of the language. The earliest list processing language was in fact IPL developed in the mid 1950’s by Simon, Newell and Shaw. Lisp itself was conceived by John McCarthy and students in the late 1950’s for use in the newly-named field of artificial intelligence. It caught on quickly in MIT’s AI Project, was implemented on the IBM 704 and by 1962 to spread through other AI groups. AI is still the largest application area for the language, but the removal of many of the flaws of early versions of the language have resulted in its gaining somewhat wider acceptance. One snag with Lisp is that although it started out as a very pure language based on mathematic logic, practical pressures mean that it has grown. There were many dialects which threaten the unity of the language, but recently there was a concerted effort to develop a more standard Lisp, viz. Common Lisp. Other Lisps you may hear of are FranzLisp, MacLisp, InterLisp, Cambridge Lisp, Le Lisp, ... Some good things about Lisp are: • Lisp is an early example of an interpreted language (though it can be compiled).
    [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]
  • 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]
  • 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]
  • Absolute BSD—The Ultimate Guide to Freebsd Table of Contents Absolute BSD—The Ultimate Guide to Freebsd
    Absolute BSD—The Ultimate Guide to FreeBSD Table of Contents Absolute BSD—The Ultimate Guide to FreeBSD............................................................................1 Dedication..........................................................................................................................................3 Foreword............................................................................................................................................4 Introduction........................................................................................................................................5 What Is FreeBSD?...................................................................................................................5 How Did FreeBSD Get Here?..................................................................................................5 The BSD License: BSD Goes Public.......................................................................................6 The Birth of Modern FreeBSD.................................................................................................6 FreeBSD Development............................................................................................................7 Committers.........................................................................................................................7 Contributors........................................................................................................................8 Users..................................................................................................................................8
    [Show full text]
  • PUB DAM Oct 67 CONTRACT N00014-83-6-0148; N00014-83-K-0655 NOTE 63P
    DOCUMENT RESUME ED 290 438 IR 012 986 AUTHOR Cunningham, Robert E.; And Others TITLE Chips: A Tool for Developing Software Interfaces Interactively. INSTITUTION Pittsburgh Univ., Pa. Learning Research and Development Center. SPANS AGENCY Office of Naval Research, Arlington, Va. REPORT NO TR-LEP-4 PUB DAM Oct 67 CONTRACT N00014-83-6-0148; N00014-83-K-0655 NOTE 63p. PUB TYPE Reports - Research/Technical (143) EDRS PRICE MF01/PC03 Plus Postage. DESCRIPTORS *Computer Graphics; *Man Machine Systems; Menu Driven Software; Programing; *Programing Languages IDENTIF7ERS Direct Manipulation Interface' Interface Design Theory; *Learning Research and Development Center; LISP Programing Language; Object Oriented Programing ABSTRACT This report provides a detailed description of Chips, an interactive tool for developing software employing graphical/computer interfaces on Xerox Lisp machines. It is noted that Chips, which is implemented as a collection of customizable classes, provides the programmer with a rich graphical interface for the creation of rich graphical interfaces, and the end-user with classes for modeling the graphical relationships of objects on the screen and maintaining constraints between them. This description of the system is divided into five main sections: () the introduction, which provides background material and a general description of the system; (2) a brief overview of the report; (3) detailed explanations of the major features of Chips;(4) an in-depth discussion of the interactive aspects of the Chips development environment; and (5) an example session using Chips to develop and modify a small portion of an interface. Appended materials include descriptions of four programming techniques that have been sound useful in the development of Chips; descriptions of several systems developed at the Learning Research and Development Centel tsing Chips; and a glossary of key terms used in the report.
    [Show full text]
  • The Evolution of Lisp
    1 The Evolution of Lisp Guy L. Steele Jr. Richard P. Gabriel Thinking Machines Corporation Lucid, Inc. 245 First Street 707 Laurel Street Cambridge, Massachusetts 02142 Menlo Park, California 94025 Phone: (617) 234-2860 Phone: (415) 329-8400 FAX: (617) 243-4444 FAX: (415) 329-8480 E-mail: [email protected] E-mail: [email protected] Abstract Lisp is the world’s greatest programming language—or so its proponents think. The structure of Lisp makes it easy to extend the language or even to implement entirely new dialects without starting from scratch. Overall, the evolution of Lisp has been guided more by institutional rivalry, one-upsmanship, and the glee born of technical cleverness that is characteristic of the “hacker culture” than by sober assessments of technical requirements. Nevertheless this process has eventually produced both an industrial- strength programming language, messy but powerful, and a technically pure dialect, small but powerful, that is suitable for use by programming-language theoreticians. We pick up where McCarthy’s paper in the first HOPL conference left off. We trace the development chronologically from the era of the PDP-6, through the heyday of Interlisp and MacLisp, past the ascension and decline of special purpose Lisp machines, to the present era of standardization activities. We then examine the technical evolution of a few representative language features, including both some notable successes and some notable failures, that illuminate design issues that distinguish Lisp from other programming languages. We also discuss the use of Lisp as a laboratory for designing other programming languages. We conclude with some reflections on the forces that have driven the evolution of Lisp.
    [Show full text]
  • Allegro CL User Guide
    Allegro CL User Guide Volume 1 (of 2) version 4.3 March, 1996 Copyright and other notices: This is revision 6 of this manual. This manual has Franz Inc. document number D-U-00-000-01-60320-1-6. Copyright 1985-1996 by Franz Inc. All rights reserved. No part of this pub- lication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means electronic, mechanical, by photocopying or recording, or otherwise, without the prior and explicit written permission of Franz incorpo- rated. Restricted rights legend: Use, duplication, and disclosure by the United States Government are subject to Restricted Rights for Commercial Software devel- oped at private expense as specified in DOD FAR 52.227-7013 (c) (1) (ii). Allegro CL and Allegro Composer are registered trademarks of Franz Inc. Allegro Common Windows, Allegro Presto, Allegro Runtime, and Allegro Matrix are trademarks of Franz inc. Unix is a trademark of AT&T. The Allegro CL software as provided may contain material copyright Xerox Corp. and the Open Systems Foundation. All such material is used and distrib- uted with permission. Other, uncopyrighted material originally developed at MIT and at CMU is also included. Appendix B is a reproduction of chapters 5 and 6 of The Art of the Metaobject Protocol by G. Kiczales, J. des Rivieres, and D. Bobrow. All this material is used with permission and we thank the authors and their publishers for letting us reproduce their material. Contents Volume 1 Preface 1 Introduction 1.1 The language 1-1 1.2 History 1-1 1.3 Format
    [Show full text]
  • Bash . . Notes, Version
    2.2 Quoting and literals 4. ${#var} returns length of the string. Inside single quotes '' nothing is interpreted: 5. ${var:offset:length} skips first offset they preserve literal values of characters enclosed characters from var and truncates the output Bash 5.1.0 notes, version 0.2.209 within them. A single (strong) quote may not appear to given length. :length may be skipped. between single quotes, even when escaped, but it Negative values separated with extra space may appear between double (weak) quotes "". Remigiusz Suwalski are accepted. ey work quite similarly, with an exception that the 6. uses a default value, if shell expands any variables that appear within them ${var:-value} var August 19, 2021 is empty or unset. (pathname expansion, process substitution and word splitting are disabled, everything else works!). ${var:=value} does the same, but performs an assignment as well. Bash, a command line interface for interacting with It is a very important concept: without them Bash the operating system, was created in the 1980s. splits lines into words at whitespace characters – ${var:+value} uses an alternative value if 1 (Google) shell style guide tabs and spaces. See also: IFS variable and $'...' var isn’t empty or unset! and $"..." (both are Bash extensions, to be done). e following notes are meant to be summary of a 2.4.4 Command substitution style guide written by Paul Armstrong and too many Avoid backticks `code` at all cost! To execute commands in a subshell and then pass more to mention (revision 1.26). 2.3 Variables their stdout (but not stderr!), use $( commands) .
    [Show full text]
  • ESA: a CLIM Library for Writing Emacs-Style Applications
    ESA: A CLIM Library for Writing Emacs-Style Applications Robert Strandh Troels Henriksen LaBRI, Université Bordeaux 1 DIKU, University of Copenhagen 351, Cours de la Libération Universitetsparken 1, Copenhagen 33405 Talence Cedex [email protected] France [email protected] David Murray Christophe Rhodes ADMurray Associates Goldsmiths, University of London 10 Rue Carrier Belleuse, 75015 Paris New Cross Road, London, SE14 6NW [email protected] [email protected] ABSTRACT style applications. The central distinguishing feature of an We describe ESA (for Emacs-Style Application), a library Emacs-style application, for our purposes, is that it uses for writing applications with an Emacs look-and-feel within short sequences of keystrokes as the default method of in- the Common Lisp Interface Manager. The ESA library voking commands, and only occasionally requires the user to takes advantage of the layered design of CLIM to provide a type the full name of the command in a minibuffer. A spe- command loop that uses Emacs-style multi-keystroke com- cial keystroke (M-x) is used to invoke commands by name. mand invocation. ESA supplies other functionality for writ- This interaction style is substantially different from the one ing such applications such as a minibuffer for invoking ex- provided by CLIM by default, and therefore required us to tended commands and for supplying command arguments, write a different CLIM top level. Fortunately, CLIM was Emacs-style keyboard macros and numeric arguments, file designed to make this not only possible but fairly straight- and buffer management, and more. ESA is currently used forward, as the implementation of a replacement top level in two major CLIM applications: the Climacs text editor can build on the protocol layers beneath, just as the default (and the Drei text gadget integrated with the McCLIM im- top level is built.
    [Show full text]
  • The Complete Freebsd
    The Complete FreeBSD® If you find errors in this book, please report them to Greg Lehey <grog@Free- BSD.org> for inclusion in the errata list. The Complete FreeBSD® Fourth Edition Tenth anniversary version, 24 February 2006 Greg Lehey The Complete FreeBSD® by Greg Lehey <[email protected]> Copyright © 1996, 1997, 1999, 2002, 2003, 2006 by Greg Lehey. This book is licensed under the Creative Commons “Attribution-NonCommercial-ShareAlike 2.5” license. The full text is located at http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode. You are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must attribute the work in the manner specified by the author or licensor. • Noncommercial. You may not use this work for commercial purposes. This clause is modified from the original by the provision: You may use this book for commercial purposes if you pay me the sum of USD 20 per copy printed (whether sold or not). You must also agree to allow inspection of printing records and other material necessary to confirm the royalty sums. The purpose of this clause is to make it attractive to negotiate sensible royalties before printing. • Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. • For any reuse or distribution, you must make clear to others the license terms of this work. • Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above.
    [Show full text]