Heading:

Title

Page Numbers: Yes X: 527 Y: 10.5"

Inter-Office Memorandum

ToCedar InterestDateDate

FromAuthorLocationPalo Alto

SubjectTitleOrganizationCSL

XEROX

Filed on: [Ivy]<CedarDocs>Location

Description of the files comprising the release of the package or whatever..

Definitions files:

DefsFile1.bcd,
DefsFilen.bcd
Implementation:
Impl1.bcd,
Impln.config
etc.

Introduction

Text text text..

First Major Topic

Text is in font 0 (TimesRoman 10) Declarations of Mesa types and variables are in font 6 (Helvetica 10), bold. When they first appear in a definitional context, they are also italicized.

Subheading

Text text text..

Further Subsections

Type, variable, procedure, and error definitions are extracted from the corresponding definitions files, formatted as shown in the following examples. These were modeled after the Pilot manual. Everything is Helvetica bold; interface names and Mesa reserved words are in font 7 (Helvetica 8.) All names are fully qualified, and if a type definition is simply a copy of another, the real definition is supplied along with the renaming definition.

ClassInstream.Instream: TYPE = REF InstreamObject;

ClassInstream.Cause: TYPE = MACHINE DEPENDENT {none(0),
strobeDown(1), strobeUp(2), heldDown(4), heldUp(10B), canBeChord(20B)};

ClassInstream.MousePosition: TYPE = Interminal.MousePosition;

Interminal.MousePosition: TYPE = MACHINE DEPENDENT RECORD [
mouseX: CARDINAL, mouseY: CARDINAL];

ClassInstream.EventIncorrect: ERROR[e: Event];

Discussion of functions and types may preceed or follow the definitions; Except that they appear on their own lines and in funny fonts, the definitions should occur naturally within the prose discussions. Fine points, as usual, appear in font 0.

ClassInstream.GetEvent: PROCEDURE[self: ClassInstream.Instream] RETURNS [e: ClassInstream.Event];

More discussion.