[Indigo]<Mesa>Doc>Muhb>MUHB3.bravo!1

Page Numbers: Yes First Page: 5 X: 527 Y: 10.5"
Margins: Binding: 13
Odd Heading: Not-on-first-page

The following list enumerates resources that may be of interest to Mesa programmers. They can all be obtained through the support group.

Complete reference on the language, syntax, and use of Mesa. See also the Compiler update memo for new language features in Mesa 6.

Describes configurations of the Mesa system software and the components which comprise them.

Describes the current release of the Mesa debugger.

Describes the procedural interface to the Mesa Ftp (file transfer) Package.

Describes the procedural interface to the Pup Package. Pups (PARC Universal Packets) represent the lowest level interface to the Ethernet communications network.

Describes facilities for adding user generated facilities to the debugger.

Describes as a small executive for controlling the compilation, binding, and debugging of applications software This package greatly speeds up the compile—bind—debug cycle when small changes are involved.

Performance Mesaurement Tool
Control Transfer Counting Tool

Describe facilities for measuring program performance.

Change Summary
Compiler Update
Binder Update
System Update
XMesa Update
Debugger Update
Utilities Update
Pup and Ftp Update

These memos describe the changes made to Mesa since the last release.

Describes some of the novel features of Mesa using a number of examples oriented towards the systems programmer. It concentrates on compile-time checking, interfaces, and modularity. It is somewhat out of date in that it describes Mesa 1.

Discusses issues involved in using Mesa for systems programming (written by the designers of the language). It is recommended for those interested in the philosophy behind the language (not for the beginner).

Mesa: A Designer’s User Perspective Febuary 28, 1978

Discusses data typing, constructors, and signals as conceived by the designers and how they worked out in practice.

The Impact of Mesa on System Design September, 1979

Describes the use of interfaces and configurations in the development of Pilot. It focuses on how the scope of interfaces was limited and modularity preserved without sacrificing strict type checking.

Pilot: A Software Engineering Case Study September, 1979

Discusses the various tools and techniques used in the development of Pilot. It lists strengths and deficiencies that were observed during the different steps of the development cycle.

Experience with Processes and Monitors in Mesa February, 1980

Discusses the use of monitors for dealing with concurrency is systems of substantial size.

<Mesa>Mesa.signals
<Mesa>Compiler.signals
<Mesa>XDebug.signals

*.signals contains a list of signal names, values, and global frame addresses for various Mesa components. These can be useful for interpreting signal values displayed by the debugger when it has insufficient symbols to give the names symbolically.

A User.cm file set up with the Mesa Bravo macros, Gacha10 for the editing font, and minimal printing fonts.

The command files used for setting up a basic Mesa disk (as described in section 1.1).

A .strike version of Gacha10 suitable for use in the Mesa Debugger or Tajo.

[Maxc1]<Secretary>MesaUsers.dl (or MesaUsers↑ to Laurel).

Distribution list for messages to the Mesa user community. If you wish to get on this list, talk to your secretary or <SDSupport>.

There have been a series of videotapes prepared which describe various features of the language and runtime environment. See a member of your support group for further details on the tapes that are currently available and where to get them.