DOCSLIB.ORG

Web (& Print) Log (2003, 2004)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Web (& Print) Log (2003, 2004) Web (& Print) Log (2003, 2004) Gene Michael Stover created 2003 May 1 updated Friday, 2004 December 31 2 Copyright c 2003, 2004 Gene Michael Stover. All rights reserved. Permission to copy, store, & view this document unmodified & in its entirety is granted. Jump to (Section ??). Contents 1 May 2003 13 1.1 3May2003 .............................. 13 1.1.1 WhatamIdoing? ...................... 13 1.1.2 HierarchicalIndexonaWebSite . 13 1.2 21May ................................ 14 1.2.1 RedWhite&Blue:R.I.P. 14 1.3 23May ................................ 14 1.3.1 Digital Restrictions Manglement . 14 1.3.2 AlanTuring.......................... 16 1.4 27May ................................ 16 1.4.1 IndependentVideo GameDevelopers. 16 2 June 2003 19 2.1 10June ................................ 19 2.1.1 VirtualWorldExchangeLanguage . 19 2.2 11June ................................ 21 2.2.1 TheMatrix,Reloaded . 21 2.3 14June ................................ 21 2.3.1 Implementing a MUD with Lisp . 21 2.4 Sunday,15June ........................... 24 2.4.1 VirtualorReality? . 24 2.5 Monday,16June ........................... 24 2.5.1 MusicinMiddleEarth. 24 2.6 Sunday,22June ........................... 25 2.6.1 Manvs.Machine ....................... 25 2.6.2 Cats&Bunnies........................ 25 2.6.3 ADefinition.......................... 25 2.7 Friday,27June ............................ 26 2.7.1 ProgrammingContest . 26 2.7.2 TheBushAdministrationLies LiesLies . 26 3 4 CONTENTS 3 July 2003 27 3.1 2July ................................. 27 3.1.1 NationalDoNotCallRegistry . 27 3.1.2 BadNumbers......................... 27 3.2 3July2003 .............................. 28 3.2.1 Law&VirtualWorlds . 28 3.3 6July2003 .............................. 29 3.3.1 AnimeGirlfriend . 29 3.4 Monday,7July2003 ......................... 29 3.4.1 VirtualWorldArticles . 29 3.5 Tuesday,8July2003......................... 29 3.5.1 WebDefacingContestDebunkery . 29 3.5.2 CatorRabbit? ........................ 30 3.5.3 SeanGorman......................... 30 3.6 Wednesday,9July .......................... 31 3.6.1 VirtualRape&FreedomofSpeech . 31 3.6.2 TheSimsTurnCriminal. 32 3.7 Thursday,10July .......................... 32 3.7.1 ProgrammingMOO .. .. .. .. .. .. .. .. .. 32 3.7.2 XeroxParc .......................... 32 3.7.3 Defacer’sChallenge . 33 3.8 Friday,11July ............................ 33 3.8.1 MoreReadingaboutMUDs . 33 3.9 Friday,18July ............................ 34 3.9.1 IraqScandal?......................... 34 3.10Monday,21July ........................... 34 3.11Tuesday,22July ........................... 35 3.12 Wednesday,23July. 35 3.13Thursday,24July .......................... 35 3.14Friday,25July ............................ 36 3.15 Wednesday,30July. 37 3.15.1 The“SCOIsABastard”Files . 37 3.15.2 LiesLieinIraq ........................ 37 4 August 2003 39 4.1 Sunday,3August........................... 39 4.2 Tuesday,5August .......................... 39 4.2.1 OriginofLispNotation . 39 4.3 Saturday,9August.......................... 40 4.3.1 SilentHill3.......................... 40 4.4 Tuesday,12August2003. 41 4.4.1 DCOMSecurityHole . 41 4.5 Wednesday,13August . 41 4.5.1 ProgrammingGames. 41 4.5.2 XboxInternals ........................ 42 4.5.3 GamesProgramming. 43 CONTENTS 5 4.6 Friday,15August2003. 43 4.6.1 Blackout? ........................... 43 4.6.2 TheBlasterworm ...................... 43 4.6.3 MoreMicrosoft ........................ 44 4.6.4 OhNoIt’sSCO ....................... 44 4.6.5 GNUservershacked . 44 4.6.6 Others............................. 45 4.7 Sunday,17August2003 . 45 4.8 Monday,18August.......................... 45 4.9 Tuesday,19August.......................... 45 4.9.1 MoreSCO........................... 45 4.9.2 COMvs.RPC ........................ 46 4.10 Wednesday,20August . 46 4.10.1 .Net&RPC ......................... 46 4.11 Thursday,21August . 46 4.11.1 Tarotcards .......................... 46 4.11.2 Polybius............................ 47 4.11.3 Religioninvideogames . 47 5 September 2003 49 5.1 Tuesday,2September .. .. .. .. .. .. .. .. .. .. 49 5.1.1 Xbox ............................. 49 5.2 Wednesday,10September . 49 5.2.1 GameProgramming . 49 5.2.2 SecurityatMicrosoft. 50 5.2.3 MoreSCO........................... 50 5.3 Thursday,11September2003 . 51 5.3.1 Games............................. 51 5.4 Friday,12September2003. 51 5.4.1 WebServerinLisp.. .. .. .. .. .. .. .. .. 51 5.5 Monday,15September. 53 5.6 Friday,19September. 53 5.7 Monday,22September2003. 54 5.8 Tuesday,23September2003. 55 5.8.1 Whatiswork? ........................ 55 5.8.2 Regrets ............................ 55 5.9 Wednesday,24September . 55 5.9.1 SemanticWeb ........................ 56 5.9.2 GamesProgramming. 57 5.10 Thursday,25September . 57 5.10.1 The Domain Name System Situation . 57 5.11 Monday,29September. 61 5.11.1 TheModern,Corporate,World . 61 5.11.2 RandomThings ....................... 61 5.11.3 WebServices ......................... 61 5.12 Tuesday,30September. 62 6 CONTENTS 6 October 2003 65 6.1 Wednesday,1October . 65 6.2 Thursday,2October . .. .. .. .. .. .. .. .. .. .. 65 6.3 Friday,3October........................... 67 6.3.1 GamesProgramming. 67 6.4 Saturday,4October2003 . 67 6.5 Sunday,5October2003 . 68 6.6 Monday,6October.......................... 68 6.6.1 Hasthishappenedtoyou? . 68 6.7 Friday,10October .......................... 69 6.8 Sunday,12October.......................... 69 6.8.1 The Problemwith Winders Programming . 69 6.9 Wednesday,15October . 70 6.10 Sunday,19October2003. 70 6.11 Monday,20October . .. .. .. .. .. .. .. .. .. .. 70 6.12 Tuesday,21October . 70 6.13 Thursday,23October . 71 6.13.1 MexicanOut-sourcing . 71 6.14 Monday,27October . .. .. .. .. .. .. .. .. .. .. 71 6.14.1 GamesProgramming&Virtual Worlds . 71 6.15 Tuesday,29October . 72 6.15.1 TheWaronTerrorism . 72 6.16 Maybethereishope ......................... 72 6.16.1 GameProgramming . 72 6.16.2 China&OpenSourceSoftware . 73 6.17 Wednesday,29October . 73 6.17.1 GamesProgramming. 73 6.18 Thursday,30October . 73 6.18.1 One Problem with ProgrammingWinders . 74 6.19 Friday,31October .. .. .. .. .. .. .. .. .. .. .. 74 7 November 2003 77 7.1 Monday,3November2003. 77 7.2 Tuesday,4November2003. 78 7.3 Wednesday,5November2003 . 78 7.3.1 Solving Problems the American Way . 78 7.4 Wednesday,5November2003 . 80 7.5 Thursday,6November2003 . 80 7.5.1 Unsolicited Commercial E-mail (Spam) . 80 7.5.2 Take advantage of morphing documents . 81 7.5.3 BusinessIsn’taZero-SumGame . 81 7.5.4 Complexity of Fee Schedules for Web Services . 81 7.5.5 GameProgramming . 81 7.6 Friday,7November2003. 81 7.6.1 AspectOrientedProgramming(AOP) . 81 7.7 Sunday,9November2003 . 82 CONTENTS 7 7.8 Monday,10November2003 . 82 7.8.1 GamesProgramming. 82 7.9 Thursday,12November2003 . 82 7.9.1 ArtificialVirus ........................ 83 7.9.2 eXplicit CongestionControl ProtocolXCP . 83 7.10 Friday,14November2003 . 84 7.11 Saturday,15November2003 . 84 7.12 Monday,17November2003 . 84 7.13 Tuesday,18November2003 . 84 7.13.1 Scumbag’sCrappy Obfuscation (SCO) . 84 7.14 Wednesday,19November2003 . 85 7.15 Thursday,20November2003 . 85 7.16 Friday,21November2003 . 86 7.17 Monday,24November2003 . 86 7.18 Wednesday,26November2003 . 86 7.18.1 .Net&Competitors . 87 8 December 2003 89 8.1 Tuesday,2December2003. 89 8.1.1 Spam ............................. 89 8.2 Wednesday,3December2003 . 90 8.3 Thursday,4December2003 . 90 8.3.1 TheSicknessBehind ModernEconomies . 90 8.4 Friday,5December2003. 91 8.4.1 JscriptDictionaryObject . 91 8.5 Monday,8December2003. 92 8.6 Tuesday,9December2003. 92 8.7 Wednesday,10December2003 . 93 8.7.1 XboxHacks.......................... 93 8.8 Friday,12December2003 . 93 8.9 Monday,15December2003 . 93 8.10 Tuesday,16December2003 . 94 8.11 Wednesday,17December2003 . 94 8.12 Thursday,18December . 94 8.13 Friday,19December . 94 8.13.1 VirtualWorlds . 94 8.1429December2003 .......................... 95 8.15 Tuesday,30December2003 . 95 8.16 Wednesday,31December2003 . 95 8.16.1 ObjectOrientedObservation . 96 9 January 2004 97 9.1 Friday,1January2004. 97 9.2 2January2004 ............................ 97 9.3 Monday,5January2004. 97 9.4 Tuesday,6January2004. 98 8 CONTENTS 9.5 Wednesday,7January2004 . 98 9.6 Thursday,8January2004 . 99 9.7 Friday,9January2003. 99 9.8 Monday,12January2004 . 99 9.8.1 WhyLisp? .......................... 99 9.9 Tuesday,13January2004 . 100 9.10 Wednesday,14January2004 . 100 9.10.1 PowerPointless. 101 9.11 Sunday,18January2004. 101 9.12 Wednesday,21January . 101 9.13 Thursday,22January2004 . 102 9.14 Friday,23January2004 . 102 9.14.1 .hack.............................. 102 9.15 Tuesday,27January2004 . 102 9.15.1 WhyTime .......................... 102 9.16 Wednesday,28January2004 . 103 9.16.1 BeefIsn’tWhat’sForDinner . 104 10 February 2004 105 10.1 Wednesday,4February2004. ..
Load more

Recommended publications
  • Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della Lezione
    Sistemi operativi real-time Marco Cesati Lezione R13 Sistemi operativi real-time – II Schema della lezione Caratteristiche comuni VxWorks LynxOS Sistemi embedded e real-time QNX eCos Windows Linux come RTOS 15 gennaio 2013 Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 Sistemi operativi Di cosa parliamo in questa lezione? real-time Marco Cesati In questa lezione descriviamo brevemente alcuni dei più diffusi sistemi operativi real-time Schema della lezione Caratteristiche comuni VxWorks LynxOS 1 Caratteristiche comuni degli RTOS QNX 2 VxWorks eCos 3 LynxOS Windows Linux come RTOS 4 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS SERT’13 R13.2 Sistemi operativi Caratteristiche comuni dei principali RTOS real-time Marco Cesati Corrispondenza agli standard: generalmente le API sono proprietarie, ma gli RTOS offrono anche compatibilità (compliancy) o conformità (conformancy) allo standard Real-Time POSIX Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili VxWorks Dimensione del codice: spesso basati su microkernel LynxOS QNX Velocità e Efficienza: basso overhead per cambi di eCos contesto, latenza delle interruzioni e primitive di Windows sincronizzazione Linux come RTOS Porzioni di codice non interrompibile: generalmente molto corte e di durata predicibile Gestione delle interruzioni “separata”: interrupt handler corto e predicibile, ISR lunga
    [Show full text]
  • Μitron 4.0 Specification (Ver. 4.03.00) TEF024-S001-04.03.00/En July 2010 Copyright © 2010 by T-Engine Forum
    μITRON 4.0 Specification Ver. 4.03.00 TEF024-S001-04.03.00/en July 2010 μITRON 4.0 Specification (Ver. 4.03.00) TEF024-S001-04.03.00/en July 2010 Copyright © 2010 by T-Engine Forum. This “μITRON 4.0 Specification (Ver. 4.03.00)” was originally released by TRON ASSOCIATION which has been integrated into T-Engine Forum since January 2010. The same specification now has been released by T-Engine Forum as its own specification without modification of the content after going through the IPR procedures. T-Engine Forum owns the copyright of this specification. Permission of T-Engine Forum is necessary for copying, republishing, posting on servers, or redistribution to lists of the contents of this specification. The contents written in this specification may be changed without a prior notice for improvement or other reasons in the future. About this specification, please refer to follows; Publisher T-Engine Forum The 28th Kowa Building 2-20-1 Nishi-gotanda Shinagawa-Ward Tokyo 141-0031 Japan TEL：+81-3-5437-0572 FAX：+81-3-5437-2399 E-mail：[email protected] TEF024-S001-04.03.00/en µITRON4.0 Specification Ver. 4.03.00 Supervised by Ken Sakamura Edited and Published by TRON ASSOCIATION µITRON4.0 Specification (Ver. 4.03.00) The copyright of this specification document belongs to TRON Association. TRON Association grants the permission to copy the whole or a part of this specification document and to redistribute it intact without charge or at cost. However, when a part of this specification document is redistributed, it must clearly state (1) that it is a part of the µITRON4.0 Specification document, (2) which part was taken, and (3) the method to obtain the whole specification document.
    [Show full text]
  • Money Cheat for Champions of Norrath
    Money cheat for champions of norrath PS2 Cheats - Champions of Norrath: This page contains a list of cheats, codes, Easter eggs, tips, and other secrets for Champions of Norrath. Game Boy · Dreamcast · DVD. Champions Of Norrath: Realms Of EverQuest . Sell the duplicated inventory items for money, then repeat. Improved character. Champions of Norrath Cheats. Champions of Norrath cheats, Tips, and Codes for PS2. Also see GameShark Codes for more Champions of Norrath cheat codes. Jump to: Tip . Item and Money Duplication. You need at least one memory card. Champions of Norrath: Realms of EverQuest Cheats and Cheat Codes, PlayStation 2. items, infinite attack points and getting extra items and more money. I found this out by accident, but it was so funny I had to do it more. In the Beginning of the game load up on explodeing potions, then throw them a.., Champions. Champions of Norrath: Realms of Everquest Cheats Unlimited Money & Items The idea behind the cheat is to import your own character into a map you. Copy Items and Money; Start a two player game then press Start and select "Add/Remove Player." Import your first character to the player two. Champions of Norrath PS2 Cheats. Champions of Norrath PS2 Level 20 Character: While your character is still at level 1, hold L1 + R2 + Triangle + R3 to raise. i hope that i have helped u^^ thxx 4 watching and please leave a comment! Champions of Norrath: Realms of Everquest cheats & more for PlayStation 2 (PS2). Cheats . Sell the duplicated inventory items for money, then repeat. Sorry for the squeaking of the camera.
    [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]
  • Reality Is Broken a Why Games Make Us Better and How They Can Change the World E JANE Mcgonigal
    Reality Is Broken a Why Games Make Us Better and How They Can Change the World E JANE McGONIGAL THE PENGUIN PRESS New York 2011 ADVANCE PRAISE FOR Reality Is Broken “Forget everything you know, or think you know, about online gaming. Like a blast of fresh air, Reality Is Broken blows away the tired stereotypes and reminds us that the human instinct to play can be harnessed for the greater good. With a stirring blend of energy, wisdom, and idealism, Jane McGonigal shows us how to start saving the world one game at a time.” —Carl Honoré, author of In Praise of Slowness and Under Pressure “Reality Is Broken is the most eye-opening book I read this year. With awe-inspiring ex­ pertise, clarity of thought, and engrossing writing style, Jane McGonigal cleanly exploded every misconception I’ve ever had about games and gaming. If you thought that games are for kids, that games are squandered time, or that games are dangerously isolating, addictive, unproductive, and escapist, you are in for a giant surprise!” —Sonja Lyubomirsky, Ph.D., professor of psychology at the University of California, Riverside, and author of The How of Happiness: A Scientific Approach to Getting the Life You Want “Reality Is Broken will both stimulate your brain and stir your soul. Once you read this remarkable book, you’ll never look at games—or yourself—quite the same way.” —Daniel H. Pink, author of Drive and A Whole New Mind “The path to becoming happier, improving your business, and saving the world might be one and the same: understanding how the world’s best games work.
    [Show full text]
  • Gentlemen's Argument
    Copyright © 2007, Chicago-Kent Journal of Intellectual Property A GENTLEMEN'S AGREEMENT ASSESSING THE GNU GENERAL PUBLIC LICENSE AND ITS ADAPTATION TO LINUx Douglas A. Hass" Introduction "Starting this Thanksgiving, I am going to write a complete Unix-compatible software system called GNU (for GNU's Not Unix), and give it away free to everyone who can use it." With his post to the Usenet 2 newsgroup net.unix-wizards, 3 Richard Stallman launched a sea change in software development. In 1983, he could not have known that his lasting contribution would not be the GNU operating system, but instead the controversial software license that he would develop as its underpinning: the GNU General Public License (GPL).4 Today, the operating system most closely associated with the GPL is Linux, developed originally by Linus Torvalds, a Finnish university student.5 Research group IDC's Quarterly Server Tracker marked Linux server revenue growth at three times Microsoft Windows server growth in the first quarter of 2006, its fifteenth consecutive quarter of double-digit revenue growth. 6 British research firm Netcraft's July 2006 Web Server Survey gives Linux-based 7 Apache Web servers the largest market share among Web servers queried in its monthly survey. With Linux gaining an increasingly larger position in these markets, the validity of the GPL takes on increasing importance as well. The open source community's commercial and non-commercial members are conducting a robust debate on the intellectual property issues surrounding the GPL and Linux, its most * Douglas A. Hass, Director of Business Development, ImageStream; J.D.
    [Show full text]
  • FOSS Philosophy 6 the FOSS Development Method 7
    1 Published by the United Nations Development Programme’s Asia-Pacific Development Information Programme (UNDP-APDIP) Kuala Lumpur, Malaysia www.apdip.net Email: [email protected] © UNDP-APDIP 2004 The material in this book may be reproduced, republished and incorporated into further works provided acknowledgement is given to UNDP-APDIP. For full details on the license governing this publication, please see the relevant Annex. ISBN: 983-3094-00-7 Design, layout and cover illustrations by: Rezonanze www.rezonanze.com PREFACE 6 INTRODUCTION 6 What is Free/Open Source Software? 6 The FOSS philosophy 6 The FOSS development method 7 What is the history of FOSS? 8 A Brief History of Free/Open Source Software Movement 8 WHY FOSS? 10 Is FOSS free? 10 How large are the savings from FOSS? 10 Direct Cost Savings - An Example 11 What are the benefits of using FOSS? 12 Security 13 Reliability/Stability 14 Open standards and vendor independence 14 Reduced reliance on imports 15 Developing local software capacity 15 Piracy, IPR, and the WTO 16 Localization 16 What are the shortcomings of FOSS? 17 Lack of business applications 17 Interoperability with proprietary systems 17 Documentation and “polish” 18 FOSS SUCCESS STORIES 19 What are governments doing with FOSS? 19 Europe 19 Americas 20 Brazil 21 Asia Pacific 22 Other Regions 24 What are some successful FOSS projects? 25 BIND (DNS Server) 25 Apache (Web Server) 25 Sendmail (Email Server) 25 OpenSSH (Secure Network Administration Tool) 26 Open Office (Office Productivity Suite) 26 LINUX 27 What is Linux?
    [Show full text]
  • V850 Series Development Environment Pamphlet
    To our customers, Old Company Name in Catalogs and Other Documents On April 1st, 2010, NEC Electronics Corporation merged with Renesas Technology Corporation, and Renesas Electronics Corporation took over all the business of both companies. Therefore, although the old company name remains in this document, it is a valid Renesas Electronics document. We appreciate your understanding. Renesas Electronics website: http://www.renesas.com April 1st, 2010 Renesas Electronics Corporation Issued by: Renesas Electronics Corporation (http://www.renesas.com) Send any inquiries to http://www.renesas.com/inquiry. Notice 1. All information included in this document is current as of the date this document is issued. Such information, however, is subject to change without any prior notice. Before purchasing or using any Renesas Electronics products listed herein, please confirm the latest product information with a Renesas Electronics sales office. Also, please pay regular and careful attention to additional and different information to be disclosed by Renesas Electronics such as that disclosed through our website. 2. Renesas Electronics does not assume any liability for infringement of patents, copyrights, or other intellectual property rights of third parties by or arising from the use of Renesas Electronics products or technical information described in this document. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of Renesas Electronics or others. 3. You should not alter, modify, copy, or otherwise misappropriate any Renesas Electronics product, whether in whole or in part. 4. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of semiconductor products and application examples.
    [Show full text]
  • Lisp: Program Is Data
    LISP: PROGRAM IS DATA A HISTORICAL PERSPECTIVE ON MACLISP Jon L White Laboratory for Computer Science, M.I.T.* ABSTRACT For over 10 years, MACLISP has supported a variety of projects at M.I.T.'s Artificial Intelligence Laboratory, and the Laboratory for Computer Science (formerly Project MAC). During this time, there has been a continuing development of the MACLISP system, spurred in great measure by the needs of MACSYMAdevelopment. Herein are reported, in amosiac, historical style, the major features of the system. For each feature discussed, an attempt will be made to mention the year of initial development, andthe names of persons or projectsprimarily responsible for requiring, needing, or suggestingsuch features. INTRODUCTION In 1964,Greenblatt and others participated in thecheck-out phase of DigitalEquipment Corporation's new computer, the PDP-6. This machine had a number of innovative features that were thought to be ideal for the development of a list processing system, and thus it was very appropriate that thefirst working program actually run on thePDP-6 was anancestor of thecurrent MACLISP. This earlyLISP was patterned after the existing PDP-1 LISP (see reference l), and was produced by using the text editor and a mini-assembler on the PDP-1. That first PDP-6 finally found its way into M.I.T.'s ProjectMAC for use by theArtificial lntelligence group (the A.1. grouplater became the M.I.T. Artificial Intelligence Laboratory, and Project MAC became the Laboratory for Computer Science). By 1968, the PDP-6 wasrunning the Incompatible Time-sharing system, and was soon supplanted by the PDP-IO.Today, the KL-I 0, anadvanced version of thePDP-10, supports a variety of time sharing systems, most of which are capable of running a MACLISP.
    [Show full text]
  • Rash: from Reckless Interactions to Reliable Programs
    Rash: From Reckless Interactions to Reliable Programs William Gallard Hatch Matthew Flatt University of Utah University of Utah USA USA [email protected] [email protected] Abstract them along a spectrum of program maturity and scale. Mov- Command languages like the Bourne Shell provide a terse ing code along this scale is often viewed as a transition from syntax for exploratory programming and system interaction. “scripts” to more mature “programs,” and current research Shell users can begin to write programs that automate their aims to improve that transition, especially through grad- tasks by simply copying their interactions verbatim into a ual typing [18, 20]. In this paper, we address a point in the script file. However, command languages usually scale poorly spectrum that precedes even the “script” level of maturity: beyond small scripts, and they can be difficult to integrate command sequences in an interactive shell. into larger programs. General-purpose languages scale well, Different features and aspects of programming languages but are verbose and unwieldy for common interactive actions are well suited to different stages of program maturity. For such as process composition. example, static types are clearly useful for ensuring and We present Rash, a domain-specific command language maintaining software correctness, but types are often seen embedded in Racket. Rash provides a terse and extensible as burdensome or obstructive when writing scripts, so many syntax for interactive system administration and scripting, scripting languages eschew types. Programmers want brevity as well as easy composition of both Racket functions and and even less formality in interactive settings, so read-eval- operating system processes.
    [Show full text]
  • A Reader Framework for Guile for Guile-Reader 0.6.2
    A Reader Framework for Guile for Guile-Reader 0.6.2 Ludovic Court`es Edition 0.6.2 8 March 2017 This file documents Guile-Reader. Copyright c 2005, 2006, 2007, 2008, 2009, 2012, 2015, 2017 Ludovic Court`es 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 con- ditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. i Table of Contents A Reader Framework for Guile ................ 1 1 Introduction............................... 3 2 Overview .................................. 5 3 Quick Start................................ 7 4 API Reference............................. 9 4.1 Token Readers .............................................. 9 4.1.1 Defining a New Token Reader............................ 9 4.1.2 Token Reader Calling Convention ........................ 9 4.1.3 Invoking a Reader from a Token Reader ................. 10 4.1.4 Token Reader Library .................................. 11 4.1.5 Limitations............................................ 16 4.1.5.1 Token Delimiters .................................
    [Show full text]
  • Foreign-Function Interfaces for Garbage-Collected Programming Languages
    Foreign-Function Interfaces for Garbage-Collected Programming Languages Marcus Crestani Eberhard-Karls-Universitat¨ Tubingen¨ [email protected] Abstract Programs in high-level, garbage-collected programming languages often need to access libraries that are written in other programming languages. A foreign-function interface provides a high-level lan- guage with access to low-level programming languages and negoti- ates between the inside and the outside world by taking care of the High-Level Foreign low-level details. In this paper, I provide an overview of what differ- Programming Function External Code ent kinds of foreign-function interfaces are in use in today’s imple- Language Interface mentations of functional programming languages to help decide on the design of a new foreign-function interface for Scheme 48. I have revised several mechanisms and design ideas and compared them on usability, portability, memory consumption and thread safety. I discuss the garbage-collection related parts of foreign-function in- terfaces using Scheme as the high-level functional language and C as the external language. Figure 1. Foreign-function interface 1. Introduction Programs in functional programming languages often need to ac- This paper reflects my survey, summarizes the results, and presents cess libraries that are written in other programming languages. Scheme 48’s new foreign-function interface, which will replace the Back in 1996, Scheme 48 [10] received its first foreign-function current one in the near future. interface. Over the years, developers connected many external li- braries to Scheme 48 using this foreign-function interface. Many 1.1 Foreign-Function Interfaces other Scheme implementations use a similar foreign-function in- A foreign-function interface provides a high-level programming terface, for example Elk [12], scsh [18], and PLT Scheme’s static language with access to other (usually low-level) programming lan- foreign interface [6].
    [Show full text]