help, verify_info, check_info_segs, help_ and info_seg_ should be moved to a new bound_help_ object.

[Gary Dixon]

Recent changes suggested for info_seg_.pl1 will grow that source component beyond the 255 page limit on its containing source archive: bound_info_rtns_.s.archive.

Two possible remedies for this issue are:

1. Split bound_info_rtns_.s.archive in to two smaller archives: bound_info_rtns_.(1 2).s.archive. Object segments compiled from sources in each source archive would then be stored in a corresponding object archive: bound_info_rtns_.(1 2).archive. The bound_info_rtns_.bind file would be stored in bound_info_rtns_.1.archive.

2. Move all help-related source files out of the bound_info_rtns_ into a new bound_help_ object. These include: help, verify_info, list_help, and check_info_segs commands; and help_ and info_seg_ subroutines and all of their supporting utility_ subroutines. Commands that would remain in bound_info_rtns_ include: list_ref_names, print_motd, resource_usage, where, and who. Subroutines that would remain in bound_info_rtns_ include: ring0_get_, system_info_, user_info_.

I favor the second alternative above. This would permit all source files relating to help facilities to be stored in a single bound_help_.s.archive which would be larger than the remaining bound_info_rtns_.s.archive.

Either approach would allow ample room for source component growth. But the second alternative locates all help-related source to be stored together as one bound segment, with one source archive.

[Gary Dixon]

MCR10103 was registered to address this enhancement.

[Eric Swenson]

​https://s3.amazonaws.com/eswenson-multics/public/mcrs/MCR10103_bound_help_v1.0.pdf