标准ML基础库手册：ML编程指南

需积分: 9 25 浏览量更新于2024-07-21 收藏 1.31MB PDF 举报

"ML程序设计技术的详细指南，主要聚焦于Standard ML (SML)的基础库，这是SML语言的标准库，适用于所有符合标准的SML实现。本书旨在为SML程序员提供一个全面的库模块、类型和函数的描述，同时阐述了库设计的原则和理念，并与使用示例相结合。重点鼓励在严肃的系统编程中应用SML。库的主要特性包括I/O功能、大量的原始类型支持、国际化支持以及可移植的操作系统接口。这本书对于学生、专业程序员和语言设计师来说是不可或缺的参考文献。" 以下是基于给定信息的详细知识点： 1. **Standard ML (SML)**：SML是一种函数式编程语言，以其严谨的类型系统和模块系统著称。它是一种静态类型的、强类型的、纯函数式的编程语言，旨在提高代码的可靠性和可维护性。 2. **SML Basis Library**：这是SML语言的核心库，为开发者提供了基础的编程元素和功能，包括数据结构、输入/输出(I/O)、字符串处理、数学运算等，是所有SML实现必须支持的一部分。 3. **I/O支持**：库中包含了处理输入和输出的功能，这对于任何实际的程序设计都是必不可少的，使得SML能够与外部世界进行交互，如读取文件、打印输出等。 4. **原始类型集合**：SML库提供了大量的基本数据类型，如整型、浮点型、字符型等，这些是构建复杂数据结构和算法的基础。 5. **国际化支持**：考虑到全球化的软件需求，SML库包含对不同语言和文化的支持，帮助开发出能适应多种语言环境的软件。 6. **可移植的操作系统接口**：SML库提供的操作系统接口允许程序在不同的操作系统上运行，提高了代码的可移植性，减少了跨平台开发的难度。 7. **设计原则与理念**：书中不仅描述了库的使用方法，还深入探讨了设计背后的原理和理由，帮助读者理解为什么要这样设计，以及如何高效地利用这些设计。 8. **作为编程参考**：本书是程序员的实用手册，提供简洁明了的库函数描述，方便开发者查找和使用，同时通过示例和模式来加深理解和应用。 9. **目标读者**：适合学习SML的学生、专业的软件开发者以及对语言设计感兴趣的人员。无论是初学者还是经验丰富的开发者，都能从中受益。 10. **作者背景**：Emden R. Gansner，作为AT&T实验室的首席技术工作人员，同时也是多所知名大学的客座教授，他的专业知识和教学经验确保了这本书的专业性和实用性。通过以上知识点，读者可以了解到SML程序设计的基本要素，以及如何有效地利用SML基础库进行开发。

xiv PREFACE

There are certain roles the book does not attempt. As we’ve already noted, it is not a

textbook, for either the Library or SML. There are already many ﬁne books and papers

teaching the joys of writing in SML, some of which address this Library as well. When

dealing with the Library’s interface to external software such as Unix or Windows, it

assumes the reader already knows how to use them or has access to sources providing

that information.

The Library is certainly not complete; there are some glaring omissions, such as a

module for handling regular expressions or guidelines for internalization. It is assumed

that, as needs are identiﬁed and consensus is reached on the design of a structure, new

modules will be added to the Library or be standardized as a separate library. The evolution

of the Library will be reﬂected in the online version of this document, the latest version

of which can be found at

http://standardml.org/Basis

Overview of the book

The book is organized in three main parts: an overview of the Library, its structure and

conventions; a tour of the main areas covered by the Library, providing programming

tips, idioms, and examples aimed at Library users; and a set of manual pages deﬁning the

signatures and structures composing the Library.

The ﬁrst three chapters form the ﬁrst part. Chapter 1 presents the philosophy, princi-

ples, and rules concerning the design of the Library. It also notes the conventions used

in documenting the Library. The second chapter lists all of the signatures, structures,

and functions in the Library, noting their connections and whether they are optional.

Chapter 3 considers those parts of the Library that are available at the top level, outside

of any structure.

The following chapters describe some of the component areas, such as I/O and text

handling, in more depth. These chapters discuss the common themes connecting the

modules of a component, and note related assumptions and restrictions. The Library

includes some elegant solutions to certain programming tasks, but these are not necessarily

obvious from a bare presentation of the signatures. Thus, many of these chapters include

short tutorial sections that discuss how various types and functions were intended to be

used, including examples of idiomatic use.

Chapter 11 is the meat of the book, containing manual pages describing the signatures,

structures, and functors speciﬁed by the Library, and their semantics. The modules are

presented in alphabetical order. Generic modules, those with multiple possible implemen-

tations, are gathered under their deﬁning signature. Thus, the Char structure is discussed

in the CHAR section. Each non-generic module, those with a unique implementation, such

as Timer, heads its own section shared with its signature. Signiﬁcant substructures, for

example, Posix.IO also rate their own sections.

2 CHAPTER 1. INTRODUCTION

Some goals in designing the Library worked toward its expansion. One, suggested

above, was the desire for the Library to be “complete enough.” If using a type provided

by the Library, the programmer should be able to look in the deﬁning structure and ﬁnd

the right function or, at least, the functions needed to build the desired function easily.

In addition, the Library attempts to provide similar functions in similar contexts. Thus,

the traditional app function for lists, which applies a function to each member of a list,

has also been provided for arrays and vectors.

An opposite design force has been the desire to keep the Basis library small. In gen-

eral, a function has been included only if it has clear or proven utility, with additional

emphasis on those that are complicated to implement, require compiler or runtime sys-

tem support, or are more concise or efﬁcient than an equivalent combination of other

functions. Some exceptions were made for historical reasons or for perceived user con-

venience.

The SML language has the rare property of being a practical, general-purpose pro-

gramming language possessing a well-deﬁned, indeed formal, semantics. Following

in this spirit, some SML-based libraries, e.g., CML [Rep99], build on this precision by

supplying their own formal semantics. Although we viewed this goal as beyond what we

could provide for the Basis library, we still felt very strongly that the functions included

here should be deﬁned as precisely and clearly as possible. In some cases, we have

deﬁned the meaning of basis functions via reference implementations. We want SML

programs to be deterministic (aside from their interaction with the external world), and

so we specify the traversal order for higher-level functions such as List.map.The

description of a function provides the dynamic constraints on the arguments, such as

that an integer index into an array must be less than the length of the array, and relates

what happens when a function invocation violates these constraints, typically the raising

of a particular exception. We have tried to stipulate completely the format of return val-

ues, so that, when a type’s representation is visible, the programmer will know what to

expect concretely, not just abstractly. We have avoided unspeciﬁed or implementation-

dependent results whenever possible. Some functions were excluded from the Library

because we could not provide a clean speciﬁcation for the function’s behavior.

1.1 Design rules and conventions

In designing the Library, we have tried to follow a set of stylistic rules to make library

usage consistent and predictable, and to preclude certain errors. These rules are not

meant to be prescriptive for the programmer using or extending the Library. On the

other hand, although the Library itself ﬂouts the conventions on occasion, we feel the

rules are reasonable and helpful and would encourage their use.

剩余486页未读，继续阅读

zbh24

粉丝: 2
资源: 4

标准ML基础库手册：ML编程指南

ML程序设计教程++（第二版）

ML程序设计语言第二版

ML程序设计教程（第二版）及答案

ml程序设计语言 pdf

LDPC 码编/译码程序设计

ml302的mqtt协议

汇编语言。'ml' 不是内部或外部命令，也不是可运行的程序 或批处理文件。

安卓使用中移ML307r 4G模块

java ml介绍_Java学习笔记一：数据类型I

最新资源

汇编语言。'ml' 不是内部或外部命令，也不是可运行的程序或批处理文件。