1 2019-05-25 Errata for Standards Manual
2
3 Function: This info segment provides errata and addenda information
4 for the Multics manual AN82-00 titled:
5
6 STANDARDS
7 SYSTEM DESIGN'S NOTEBOOK
8
9
10 2019-05-25 Information for MR 12.7:
11
12 pg 11-2 under "SYNTAX OF INFO SEGMENTS"
13 Replace the "Title" paragraph with the following:
14
15 Title
16
17 Some rules apply to all three types of info segments. The
18 first line in each info segment or entrypoint description within
19 a subroutine info segment must be a brief title line, beginning
20 with the date of the last modification. The title should be
21 appropriate for a table of contents; for command or subroutine
22 descriptions it will give the names of the program including
23 abbreviations. The date should be in iso_date format.
24
25 Examples of title lines:
26
27 2019-05-24 AN82 Errata for Standards Manual
28 1985-10-10 validate_info_seg, vis
29
30 1985-09-23 ioa_
31 ...
32 :Entry: ioa_: nnl: 1981-09-19 ioa_, ioa_$nnl
33
34 The last example above shows titles for a subroutine with several
35 entrypoints. The first title line uses the standard title format
36 for the introductory section of the info segment; this section
37 describes the purpose and common characteristics of all the
38 subroutine's entrypoints. Subsequent sections describe each
39 entrypoint or group of entrypoints sharing a common calling
40 sequence. Each section begins with an :Entry: title line naming
41 the entrypoints followed by a typical title line with iso_date
42 and the full subroutine names described by that section. The
43 :Entry: and colon-separated names allow the help command to skip
44 to the description of a particular entrypoint, and to produce
45 output for its list_entry_points request.