1 11/19/84 bind.changes
 2 
 3 The binder has been changed to allow an unlimited number of object
 4 components to be bound.  (The bound segment may not, however, exceed
 5 one segment.)
 6 
 7 The old limit of 30 has been removed from the number of input and
 8 updated archives.
 9 
10 Standalone segments are now accepted by using the new -segment control
11 argument.  Also see the new -archive control argument.
12 
13 The -bindfile control argument has been added which allows the user to
14 override the bindfile seletion method.
15 
16 Zero-length objects will no longer result in fatal errors.  A warning
17 is issued and the object is ignored.
18 
19 The bindfile parsing routine has been rewritten using the reduction
20 compiler.  As a result, the error messages look slightly
21 different than before, e.g.,
22 
23                     ERROR 22 SEVERITY 3 in LINE 20
24                     Objectname foo not mentioned in order statement
25 
26 2 new bindfile master keywords have been added: Partial_Order and
27 Ignore.
28 
29 For more information on the above see the binder help file (bind.info).
30 
31 Error numbers 16, 22, and 23 in the binder error list have been fixed.
32 Note that error 16 caused adding the names of all the components to
33 the bound segment if the "Addname:;" statement were included in the
34 bindfile.  The code now conforms to the documentation and only the
35 names of those components that have external symbols retained will be
36 added.
37 
38 When adding names, the binder now uses nd_handler_ to resolve name
39 duplications.  This may cause names to be removed from other entries
40 in the same directory.  Before removing the last name from another
41 segment, the user is queried if that entry is to be deleted.
42 
43 Error 17 has been partially fixed.  If "syntax" errors are found in
44 the bindfile, the existing bound segment will not be truncated.
45 "Semantic" errors, e.g.
46           ...
47           objectname: foo;
48           retain: bar;
49           ...
50 where entrypoint "bar" does not exist in "foo", are detected upon
51 examining the individual object components when rebuilding of the
52 bound segment has already started.