DOCSLIB.ORG

[Special-PDF] Olin Shivers Scsh Manual High School

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
[Special-PDF] Olin Shivers Scsh Manual High School Olin Shivers Scsh Manual High School Download Olin Shivers Scsh Manual High School Iain Ferguson, Edward Martin and Burt Kaufman. Foreword by Daniel Friedman. "The Schemer's Guide: Second Edition" Schemers Inc, Ft. Lauderdale, FL, 1995. (see EdScheme entry in [2-2]) 330 pages, ISBN 0-9628745-2- 3, $35.95. This book assumes no previous programming experience and is ideal for high school or college students. Olin Shivers’ Acknowledgements to the Scsh Reference Manual: Who should I thank? My so-called “colleagues,” who laugh at me behind my back, all the while becoming famous on my work? My worthless graduate students, whose computer skills appear to be limited to downloading bitmaps off of netnews? 8 May 2006. Olin Shivers, Brian D. Carlstrom, Martin Gasbichler, and Mike Sperber. Around with computers,'' go to med school, and become a radiologist? In Allegro CL 4.1 [SPARC; R1], the rule of thumb is that for less than 24 elements, linear search using alists beats hashing. In Lucid CL 4.0.1 HP 9000-700, the break-even point is at 10 elements. The break-even points vary in other lisps from as low as 4 elements to as high as 100 elements. Scsh is limited to 32-bit platforms but there is a development version against the latest Scheme 48 that works in 64-bit mode. It is free and open-source software released under a BSD license. Features. Scsh includes these notable features: Library support for list, character, and string manipulations; A copy of the 1983-84 high school football, volleyball and basketball schedules. 8. A copy of the 1983-84 budget summary sheets for the school district. "Mentor's Manual", 1953, Grand Lodge F.Olin Shivers's message on the SCSH module system; On Lisp is a great Lisp book, but it's not for beginners. Online JavaScript beautifier: Beautify, unpack or deobfuscate JavaScript and HTML, make JSON-JSONP readable, etc. Open Dylan: compiles to native code, has an excellent IDE with support for incremental development, and has great library.24 Sep 2005. Olin Shivers pro- vided tools. Explicit handling of continuations is high. Moreover. Ence manual of a loop construct was consulted when reading other people's. Construct—but rather as of great educational and entertaining value. It should. Scheme bindings for all ncurses functions using scsh's foreign. Scsh Reference Manual. Postscript. Olin Shivers says he's feeling a lot better now. He's offering dissertation advice and explaining the History of T, which is a good sign. However, his out-of-date homepage is missing his popular quote that explains his guiding philosophy: I object to doing things that computers can do. Scsh Reference Manual For Scsh release 0.3 December 25, 1994 Olin Shivers and Brian D. Carlstrom December 21, 1994 – 02:25 DRAFT friends from high school, Janelle Louie, Eric Lee, and Alisa Patel, filled my. To Hillary & Olin Shivers, who have been the best neighbors I could ever hope for. (Notice, however, that I did not seek to replicate Olin's SCSH Reference Manual. Olin Shivers in comp.Lang.Scheme, April 2000 * If people are sane, if the world keeps moving forward, if we intellectuals keep fulfilling our duty of education, then good things will spread, and happiness will rain on earth. Xah Lee in comp.Lang.Lisp, July 2000. Related Links. The Daily WTF– curious perversions in information technology The design paper on the Scheme shell scsh. A Scheme shell. Ewblock Olin Shivers. Ewblock \emph{Lisp and Symbolic Computation}, to appear. (Also available as Technical report TR-94-10, Dept. Of Computer Science, University of Hong Kong, and Technical report TR-635, Laboratory for Computer Science, MIT.) The Bromfield School (Harvard Public Schools) (02-Jul-18; 12-Dec-20). Ygyde (oligosynthetic, designed for high information density) (17-Nov-11; 13- Dec-20); Zhyler (a. Dylan Reference Manual (7 Apr 1998) (11-Sep-17; 30-Dec-20). (04-Apr-09; 15-Jan-20; 26- Nov-20); History of T (Olin Shivers) (16-Mar-10; 31-Jan-21). April 29, 2004. The 2004 edition of The American Medical Directory cardiology, radiology, xp fxpuq pe, Marlene Jenkins; April 28, 2004. The 2004 edition of The American Medical Directory disease, surgery, obstetrics, lxl u, Sal Hickman And I owe a huge thank you to Hillary & Olin Shivers, who have been the best neighbors I could ever hope for. (Notice, however, that I did not seek to replicate Olin’s SCSH Reference Manual acknowledgments—though I was tempted.) Originally specified in 1958, Lisp is the second-oldest high-level programming language in widespread use today. Only Fortran is older, by one year. Lisp has changed since its early days, and many dialects have existed over its history. Today, the best-known general-purpose Lisp dialects are Racket, Common Lisp, Scheme and Clojure. Scsh is limited to 32-bit platforms but there is a development version against the latest Scheme 48 that works in 64-bit mode. [1] It is free and open-source software released under a BSD license. Computer software , or simply software , is a collection of data or computer instructions that tell the computer how to work. Sheldon, Olin Shivers, Franklyn Turbak, and many others at Tech Square, for making. People who use programs place such a high level of trust in the people who write. Olin Shivers used Scheme 48 as a substrate for scsh 54], a Unix shell. Educational background of the students and researchers that use the robot. Scsh (a Scheme shell) is computer software, a type of shell for an operating system. Original author(s), Olin Shivers. The reference manual for Scsh includes a spoof Acknowledgments section. My parents, who are still waiting for me to quit "fooling around with computers," go to med school, and become a radiologist? Caterpillar Cat 426c Backhoe Parts Manual New Holland Mz18h Zero Turn Mower Tractor Owner Operators User Guide Manual Genie Garage Door Opener Ims 1000 Manual 1996 Infiniti G20 Service Repair Manual 2009 Polaris Atv Ranger Rzr 170 4 Stroke Owners Manual New 161 Hyster Transmission Repair Workshop Manual Manual 2016 Toyota Tacoma Par 36 4-lite Manual Mazda 6 Manual Transmission Fluid Type Kubota L305dt Tractor Illustrated Master Parts List Manual 73531i Manual Dexterity Barina Cd Owners Manual Chilton Repair Manual 00 Saturn Sl2 2015 Bmw R1150rt Service Manual Stm32l15xxx Flash Programming Manual Nextel User Manual Manual Camera Nexus 6p Phone Abbott Tdxflx Service Manual.
Load more

Recommended publications
  • 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]
  • Functional Package Management with Guix
    Functional Package Management with Guix Ludovic Courtès Bordeaux, France [email protected] ABSTRACT 1. INTRODUCTION We describe the design and implementation of GNU Guix, a GNU Guix1 is a purely functional package manager for the purely functional package manager designed to support a com- GNU system [20], and in particular GNU/Linux. Pack- plete GNU/Linux distribution. Guix supports transactional age management consists in all the activities that relate upgrades and roll-backs, unprivileged package management, to building packages from source, honoring the build-time per-user profiles, and garbage collection. It builds upon the and run-time dependencies on packages, installing, removing, low-level build and deployment layer of the Nix package man- and upgrading packages in user environments. In addition ager. Guix uses Scheme as its programming interface. In to these standard features, Guix supports transactional up- particular, we devise an embedded domain-specific language grades and roll-backs, unprivileged package management, (EDSL) to describe and compose packages. We demonstrate per-user profiles, and garbage collection. Guix comes with a how it allows us to benefit from the host general-purpose distribution of user-land free software packages. programming language while not compromising on expres- siveness. Second, we show the use of Scheme to write build Guix seeks to empower users in several ways: by offering the programs, leading to a \two-tier" programming system. uncommon features listed above, by providing the tools that allow users to formally correlate a binary package and the Categories and Subject Descriptors \recipes" and source code that led to it|furthering the spirit D.4.5 [Operating Systems]: Reliability; D.4.5 [Operating of the GNU General Public License|, by allowing them to Systems]: System Programs and Utilities; D.1.1 [Software]: customize the distribution, and by lowering the barrier to Applicative (Functional) Programming entry in distribution development.
    [Show full text]
  • A Tractable Scheme Implementation
    LISP AND SYMBOLIC COMPUTATION:An International Journal, 7, 315-335 (1994) © 1994 Kluwer Academic Publishers, Boston. Manufactured in The Netherlands. A Tractable Scheme Implementation RICHARD A. KELSEY [email protected] NEC Research Institute JONATHAN A. REES [email protected] M1T and Cornell University Abstract. Scheme 48 is an implementation of the Scheme programming language constructed with tractability and reliability as its primary design goals. It has the structural properties of large, compiler-based Lisp implementations: it is written entirely in Scheme, is bootstrapped via its compiler, and provides numerous language extensions. It controls the complexity that ordinarily attends such large Lisp implementations through clear articulation of internal modularity and by the exclusion of features, optimizations, and generalizations that are of only marginal value. Keywords: byte-code interpreters, virtual machines, modularity, Scheme, partial evaluation, layered design 1. Introduction Scheme 48 is an implementation of the Scheme programming language constructed with tractability and reliability as its primary design goals. By tractability we mean the ease with which the system can be understood and changed. Although Lisp dialects, including Scheme, are relatively simple languages, implementation tractability is often threatened by the demands of providing high performance and extended functionality. The Scheme 48 project was initiated in order to experiment with techniques for main- taining implementation tractability in the face of countervailing pressures and to find out what tradeoffs were involved in doing so. (The project was originally an experiment to see if a Scheme implementation could be written in a single weekend; the 48 refers to forty-eight hours.) Small Lisp implementations are usually tractable merely by virtue of being small; it is usually possible for an experienced programmer to read and understand the entire source program in a few days.
    [Show full text]
  • The Incomplete Scheme 48 Reference Manual for Release 1.8
    The Incomplete Scheme 48 Reference Manual for release 1.8 Richard Kelsey Jonathan Rees Mike Sperber A line may take us hours, yet if it does not seem a moment’s thought All our stitching and unstitching has been as nought. Yeats Adam’s Curse ii Acknowledgements Thanks to Scheme 48’s users for their suggestions, bug reports, and forbearance. Thanks also to Deborah Tatar for providing the Yeats quotation. iii Contents Contents iv 1 Introduction 1 2 User’s guide 2 2.1 Command line arguments . 2 2.2 Command processor . 3 2.3 Editing . 3 2.4 Performance . 3 2.5 Disassembler . 4 2.6 Module system . 4 2.7 Library . 6 3 Command processor 7 3.1 Current focus value and ## ..................... 7 3.2 Command levels . 8 3.3 Logistical commands . 9 3.4 Module commands . 9 3.5 Debugging commands . 9 3.6 Settings . 11 3.7 Inspection mode . 13 3.8 Command programs . 14 3.9 Building images . 15 3.10 Resource query and control . 15 3.11 Threads . 16 3.12 Quite obscure . 17 4 Module system 18 4.1 Introduction . 18 4.2 The configuration language . 19 4.3 Interfaces . 21 4.4 Macros . 22 4.5 Higher-order modules . 23 4.6 Compiling and linking . 23 iv 4.7 Semantics of configuration mutation . 23 4.8 Command processor support . 24 4.9 Configuration packages . 27 4.10 Discussion . 28 5 Libraries 30 5.1 General utilities . 30 5.2 Pretty-printing . 32 5.3 Bitwise integer operations . 32 5.4 Byte vectors .
    [Show full text]
  • A Universal Scripting Framework Or Lambda: the Ultimate “Little Language”
    A Universal Scripting Framework or Lambda: the ultimate “little language” Olin Shivers MIT AI Lab, Cambridge, Mass. 02139, USA Abstract. The “little languages” approach to systems programming is flawed: inefficient, fragile, error-prone, inexpressive, and difficult to compose. A bet- ter solution is to embed task-specific sublanguages within a powerful, syntac- tically extensible, universal language, such as Scheme. I demonstrate two such embeddings that have been implemented in scsh, a Scheme programming envi- ronment for Unix systems programming. The first embedded language is a high- level process-control notation; the second provides for Awk-like processing. Em- bedding systems in this way is a powerful technique: for example, although the embedded Awk system was implemented with 7% of the code required for the standard C-based Awk, it is significantly more expressive than its C counterpart. 1 Introduction Many programming tools are built around the idea of “little languages”—small inter- preters implementing a programming language that has been tuned to the specifics of some specialised task domain. This approach to systems-building was popularised by Unix, which provides a host of little-language processors. For example, the following Unix language interpreters all support notations tuned for specialised task domains: Task Interpreter regular-expression based string transforms sed pattern-matching awk type-setting nroff/tbl/eqn dependency-directed recompilation make file-system tree-walking find program invocation and composition sh Little languages complement the Unix “toolkit” philosophy—the operating system provides mechanisms for composing little-language based components into larger sys- tems (and, in fact, the principal interface for doing so is itself a little language, the shell).
    [Show full text]
  • Contracts Be Misunderstood (Functional Pearl)
    Oh Lord, Please Don’t Let Contracts Be Misunderstood (Functional Pearl) Christos Dimoulas, Max S. New, Robert Bruce Findler, Matthias Felleisen PLT, USA {chrdimo,maxsnew,robby,matthias}@racket-lang.org Abstract gramming language to not only express logical assertions about Contracts feel misunderstood, especially those with a higher-order their functions but also construct new forms of contracts with soul. While software engineers appreciate contracts as tools for ar- user-defined combinators. Especially in the context of languages ticulating the interface between components, functional program- that shout “domain specific languages” from every roof top—say mers desperately search for their types and meaning, completely Racket—researchers and developers ought to be able to eliminate the problems that plague sophisticated practical applications of forgetting about their pragmatics. 1 This gem presents a novel analysis of contract systems. Applied conventional contract systems. If they put their mind to it, they to the higher-order kind, this analysis reveals their large and clearly could construct linguistic mechanisms that raised the level of ex- unappreciated software engineering potential. Three sample appli- pressiveness and allowed programmers to articulate an unprece- cations illustrate where this kind of exploration may lead. dented detail of precision for a relatively low cost in terms of code. This gem demonstrates how this alternative mind set about con- Categories and Subject Descriptors D.3.3 [Programming Lan- tracts opens new possibilities. It starts with a novel conceptual guages]: Language Constructs and Features analysis of contracts, re-imagining them as an interlocking sys- tem of interposition points, linguistic constructs for contract attach- Keywords Contracts, Specifications, Language design ment, and DSLs for assembling logical assertions from rather sim- ple building blocks (section 2).
    [Show full text]
  • Vladilen Kozin
    Vladilen Kozin Clojure(Script), Racket, Emacs Lisp, TCL, Redex, OMeta, meta-programming Fall’13 Recurse Center (aka Hacker School) alum UK Tier 1 Exceptional Talent visa holder Corporate ladder Dec 2019-now Contracting gigs Jul-Dec 2019 Senior Programmer at All Street Research (London, UK) Building cognitive assistant for investment research in Clojure(Script). Front and back, AI, NLP, and more buzzwords here. Apr-Nov 2017 Senior Programmer at Droit (London, UK) Same as before but with obligatory daily commute. 2015-2017 Programmer/Consultant at Droit (remote and New York, USA) Building an expert system for compliant trading. Sneaking Clojure(Script) into unsuspecting financial giants. On any given day I could be designing DSLs, implementing compilers, parsers, rule-based engines, putting together simple browser-based GUIs and whatever else the startup life would have me do. 2014-2015 Programmer at Yandex (Moscow, Russia). Officially a member of Search Interfaces Development Infrastructure group, but mostly I wrote backend tools for source to source compilation - engines to write your template engines. If I were lucky and did it right frontend developers would get to use my work and take all the credit. 2009-2011 Equity Derivatives & Structured Products Sales at Renaissance Capital (Moscow, Russia). 2007-2009 EM Structured Solutions and Derivatives Sales at Barclays Capital (London, UK). Projects Emacs Lisp Author of multi.el - all things multiple dispatch for Emacs Lisp: type driven dispatch with protocols, ad-hoc polymorphism with multi-methods, pattern-matching and destructuring without noise with multi-patterns, case-dispatch with multi-defuns, benchmarking with multi-benchmarks. Racket Author of tilda an opinionated threading macro with self-documenting hole-markers, clause level keyword options and an implicit escape continuation.
    [Show full text]
  • Laboratory for Computer Science a Scheme Shell
    MASSACHUSETTS INSTITUTE OF TECHNOLOGY Laboratory for Computer Science Personal Information Architecture Note 3 4/94 A Scheme Shell Olin Shivers [email protected] Although robust enough for general use, adventures into the esoteric periphery of the C shell may reveal unexpected quirks. — SunOS 4.1 csh(1) man page, 10/2/89 Prologue Shell programming terrifies me. There is something about writing a sim- ple shell script that is just much, much more unpleasant than writing a simple C program, or a simple COMMON LISP program, or a simple Mips assembler program. Is it trying to remember what the rules are for all the different quotes? Is it having to look up the multi-phased interaction between filename expansion, shell variables, quotation, backslashes and alias expansion? Maybe it’s having to subsequently look up which of the twenty or thirty flags I need for my grep, sed, and awk invocations. Maybe it just gets on my nerves that I have to run two complete programs simply to count the number of files in a directory (ls | wc -l), which seems like several orders of magnitude more cycles than was really needed. Whatever it is, it’s an object lesson in angst. Furthermore, during late- night conversations with office mates and graduate students, I have formed the impression that I am not alone. In late February1, I got embroiled in a multi-way email flamefest about just exactly what it was about Unix that drove me nuts. In the midst of the debate, I did a rash thing. I claimed that it would be easy and so much nicer to do shell programming from Scheme.
    [Show full text]
  • Gauche Users' Reference
    Gauche Users' Reference version 0.9.8 Shiro Kawai ([email protected]) Copyright c 2001-2017 Shiro Kawai ([email protected]) i Table of Contents 1 Introduction :::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.1 Overview of Gauche:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Notations :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 1.2.1 Entry format:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 1.2.2 Names and namespaces ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2 Concepts :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.1 Standard conformance ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.2 Multibyte strings ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 10 2.3 Multibyte scripts ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 11 2.4 Case-sensitivity ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 2.5 Integrated object system :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 2.6 Module system ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 2.7 Compilation :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 14 3 Programming in Gauche ::::::::::::::::::::::::::::::::::::: 15 3.1 Invoking Gosh :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 15 3.2 Interactive development::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 19 3.2.1 Working in REPL::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • 2010 Workshop on Scheme and Functional Programming
    2010 Workshop on Scheme and Functional Programming Montreal,´ Quebec,´ Canada Saturday and Sunday August 21-22, 2010 2 Preface This report contains the papers presented at the Eleventh Workshop on Scheme and Functional Programming, held on Saturday and Sunday, August 21 and 22, 2010 at the Universite´ de Montreal.´ Eight papers were submitted in response to the call for papers. Each paper was evaluated by three reviewers. After due deliberation, the program committee decided to accept all papers. This year the program includes lightning talks which we hope will help the exchange of new ideas and developments between the participants. We thank Olin Shivers and Robby Findler who have graciously accepted our invitation to present their work. The Scheme Language committees will report on their progress towards the next Scheme standard. The workshop has been extended from its traditional one day format to a day and a half to accommodate all of the presentations. Finally we would like to thank Robby Findler for helping out with the formatting of the proceedings, and Virginie Allard-Cameus,´ Marie-Josee´ Boulay, and Line Pariseau for taking care of the catering and other local arrangements. Marc Feeley Universite´ de Montreal´ Organizer and Program Chair Program Committee Alan Bawden (independent consultant) Felix S. Klock II (Adobe Systems Incorporated) Olivier Danvy (Aarhus University) Jay McCarthy (Brigham Young University) Christopher Dutchyn (University of Saskatchewan) Scott McKay (ITA software) Marc Feeley (Universite´ de Montreal)´ Steering Committee William D. Clinger (Northeastern University) Christian Queinnec (Universite´ Pierre et Marie Curie) Marc Feeley (Universite´ de Montreal)´ Manuel Serrano (INRIA Sophia Antipolis) Robby Findler (Northwestern University) Olin Shivers (Northeastern University) Dan Friedman (Indiana University) Mitchell Wand (Northeastern University) 3 4 Schedule & Table of Contents Saturday, August 21 8:15 On-site registration and breakfast 9:00 Invited Talk: Eager parsing and user interaction with call/cc ........................
    [Show full text]