ChezScheme 9.5.1 用户指南：深入探索与调试

需积分: 33 149 浏览量更新于2024-07-18 收藏 2.92MB PDF 举报

本资源是一份名为《ChezScheme Version 9 用户指南》的手册，由Cisco Systems, Inc.发布，适用于深入研究Scheme语言的专业人士。手册在2005年至2018年期间根据Apache License Version 2.0进行授权，适用于ChezScheme 9.5.1版本。书中详细介绍了Scheme语言的核心概念、使用方法以及调试技巧。 **1. ** **ChezScheme Syntax** (第1章) 本章节着重讲解ChezScheme的语法特点，包括其基本构造块如表达式、变量、数据类型（如数字、符号、列表等）和函数的定义。这部分内容是理解Scheme语言的基础，有助于新用户快速上手。 **1.2. Notational Conventions** (第1章) 手册提供了一套符号和约定的指南，帮助读者在阅读和编写代码时保持一致性，如如何表示特殊字符、注释格式和代码样例的呈现方式。 **1.3. Parameters** (第1章) 这部分介绍了参数的处理方式，包括位置参数、关键字参数、可变数量参数和默认值，这对于编写可配置的函数和程序至关重要。 **2. ** **Using ChezScheme** (第2章) 本章节详细描述了如何与ChezScheme进行交互，包括命令行界面、交互式表达式编辑器的使用、互动环境的功能以及如何加载和使用库和顶层程序。此外，还讨论了优化方案和如何定制ChezScheme以满足特定需求。 **2.5. Scheme Shell Scripts** (第2章) 这部分介绍了如何编写和执行Scheme脚本，以自动化任务或创建可重复使用的工具，展示了脚本编程的强大功能。 **2.6. Optimization** (第2章) 对于性能敏感的开发者，手册解释了如何对ChezScheme代码进行优化，包括编译选项和性能调优策略。 **2.8. Building and Distributing Applications** (第2章) 涵盖了如何构建和打包应用程序，以及如何将它们分发给其他用户，包括打包成可执行文件、创建安装程序和依赖管理。 **3. Debugging** (第3章) 最后一章专门探讨了调试技术，包括如何识别和修复错误，使用内置的调试工具进行单步执行、查看内存状态和追踪程序流程。这份《ChezScheme Version 9 用户指南》提供了全面的资源，涵盖了从语言基础到高级应用开发和调试的各个环节，对于想要深入了解和实践Scheme编程的读者来说是一本不可或缺的参考书。

6 1. Introduction

• syntactic abstraction [14, 8, 17],

• modules [32],

• libraries [21],

• storage management [12, 13],

• threads [10],

• multiple return values [2],

• optional arguments [16],

• continuations [7, 25, 3],

• eq? hashtables [20],

• internal deﬁnitions, letrec, and letrec* [33, 22],

• equal? [1],

• engines [15],

• ﬂoating-point printing [4],

• code generation [18],

• register allocation [6],

• procedure inlining [31],

• proﬁling [5], and

• history of the implementation [9].

Links to abstracts and electronic versions of these publications are available at the url

http://www.cs.indiana.edu/chezscheme/pubs/.

2. Using Chez Scheme

Chez Scheme is often used interactively to supp or t program development and debugging,

yet it may also be used to create stand-alone applications with no interactive comp one nt.

This chapter describes the various way s in which Chez Scheme is typically used and, more

generally, how to get the mos t out of the system. Sections 2.1, 2.2, and 2.3 describe how one

uses Chez Scheme interactively. Section 2.4 discusses how libraries and RNRS top-level pro-

grams are us ed in Chez Scheme. Section 2.5 cover s support for writing and running Scheme

scripts, including compiled scripts and compiled RNRS top-level programs. Section 2.6 d e-

scribes how to struc tu r e and compile an application to get the most eﬃcient code p oss i bl e

out of the compiler. Secti on 2.7 describes how one can customize the startup process, e.g.,

to alter or eliminate the command-line options, to p r el oad Scheme or foreign code, or to

run Chez Scheme as a subordinate pr ogr am of another program. Section 2.8 describes how

to build applications using Chez Scheme with Petite Chez Scheme for run- t im e support.

Finally, Section 2.9 covers command-line options used when invoking Chez Scheme.

2.1. Interacting with Chez Scheme

One of the simplest and most e↵ective ways to write and test Scheme programs is to

compose them using a text editor, like vi or emacs, and test them interactively with

Chez Scheme running in a shell window. When Chez Scheme is installed with default

options, entering the command scheme at the shell’s prompt starts an interactive Scheme

session. The command petite does the same for Petite Chez Scheme. After entering t hi s

command, you should see a short greeting followed by an angle-bracket on a li ne by i t sel f ,

like this:

Chez Scheme Version 9.5.1

You also should see that the cursor is sitting one space to the ri ght of the angle-bracket.

The angle-bracket is a prompt issued by the system’s “REPL,” which stands for “Read

Eval Print Loop,” so called because it reads, evaluates , and prints an expression, then

loops back to read, evaluate, and pr i nt the next, an d so on. (In Chez Scheme,theREPL

is also called a waiter.)

10 2. Using Chez Scheme

The interaction described above uses just a few of the expeditor’s feat ures. The exped i t or’ s

remaining features are described in the following section.

Running programs may be inter r up t ed by typing the interrupt ch arac t er (typically ^C).

In response, the system enters a debug handler, which prompts for input with a break>

prompt. One of several commands may be issu ed to the break handler (followed by a

newline), including

“e” or end-of-ﬁle to exit from the han dl e r and continue,

“r” to stop execution and reset to t he current caf´e,

“a” to abort Chez Scheme,

“n” to enter a new caf´e (see bel ow),

“i” to inspect the current continuation,

“s” to display statistics about the interrupted program, and

“?” to display a list of these options.

When an exception ot h er than a warning occurs, the default exception handler prints a

message that describes the exception to the console error port. If a REPL is running, the

exception handler then returns to the REPL, where the programmer can call the debug

procedure to start up the debug handle r, if desired. The debug handler i s similar to the

break handler and allows the p r ogram mer to inspect the continuation ( control stack) of

the exception to he l p determine the cause of the problem. If no REPL is running, as is

the case for a script or top-level program run via the --script or --program command-line

options, the default except i on handler exits from the scr ip t or program after printing t h e

message. To allow scripts and top-level programs to be debugged, the default exception

handler can be forced via the debug-on-exception p ar amet e r or the --debug-on-exception

command-line option to invoke debug directly.

Developing a large program entirely in the REPL is unmanageable, and we usually even

want to store small er programs in a ﬁle f or future use. (The expeditor’s history is saved

across Scheme sessions, but there is a limit on the number of item s, so it is not a good idea

to count on a program remaini n g in the history indeﬁnitely. ) Thus, a Scheme programmer

typically creates a ﬁle containing Scheme source code using a text editor, su ch as vi, and

loads the ﬁle into Chez Scheme to test them. The conventional ﬁlename extension for

Chez Scheme source ﬁles is “.ss,” bu t the ﬁle can have any extension or even no extension

at all. A source ﬁle can be loaded during an interactive session by typi n g (load "path ").

Files to be loaded can also be named on the command line when the system is st ar t ed .

Any form that can be typed interactively can be placed in a ﬁle to be loaded.

Chez Scheme compiles source forms as it sees the m to machine code before evalu at ing

them, i.e., “just in time.” In order to speed loading of a large ﬁle or group of ﬁles, each

ﬁle can be compiled ahead of time via compile-file, which puts the compiled code into

a separate object ﬁle. For example, (compile-file "path ") compiles t he forms in the ﬁle

path .ss and places the resulting obje ct code in the ﬁle path .so. Loading a pre-compiled ﬁle

is essentially no di↵erent from loadi ng the source ﬁle, except that loading is faster since

compilation has already been done.

剩余511页未读，继续阅读

shoutyappy

粉丝: 0
资源: 1

ChezScheme 9.5.1 用户指南：深入探索与调试

快手_Scheme协议.txt

scheme语言学习资料集合

scheme简明教程

chez scheme 手册

mit-scheme手册

fluent_scheme语言手册

Fluent Scheme中文手册修订.docx

fluent——scheme简明中文手册

MIT/GNU Scheme参考手册

mit-scheme解释器和用户手册

最新资源