02/13/84 pathname_ The pathname_ subroutine contains entry points for constructing pathnames and archive component pathnames given a directory name, entry name, and optionally, an archive component name. When a directory name and an entry name are combined to form a pathname, the result may be longer than 168 characters. If truncating the pathname doesn't matter, e.g. in an error message in a call to com_err_ for another, more important error, then use the pathname_ or pathname_$component entry points. These entry points create an invalid pathname with the characters "PATHNAME TOO LONG" to let the reader know truncation occured. If truncating the pathname matters, use the pathname_$component_check entry point. Entry points in pathname_: (List is generated by the help command) :Entry: pathname_: 02/13/84 pathname_ Function: given a directory name and an entry name, returns the pathname of the entry. Syntax: declare pathname_ entry (char (*), char (*)) returns (char (168)); path = pathname_ (dirname, entryname); Arguments: path is the pathname of the entry in the given directory. (Output) dirname is the pathname of the containing directory. (Input) entryname is the entryname of the entry. (Input) Notes: If the resulting pathname is longer than 168 characters, then the last 20 characters of the result are set to " ". :Entry: component: 02/13/84 pathname_$component Function: given a directory name, an entry name, and optionally, an archive component name, constructs a pathname or an archive component pathname. Syntax: declare pathname_$component entry (char (*), char (*), char (*)) returns (char (194)); path = pathname_$component (dirname, entryname, component_name); Arguments: path is the pathname of the entry in the given directory, or is an archive component pathname. (Output) dirname is the pathname of the containing directory. (Input) entryname is the entryname of the entry. (Input) component_name is the name of an archive component, or is null. (Input) Notes: If component_name is not null, the archive suffix on the entryname is optional, and is assumed if not specified. If component_name is not null and entryname ends with the archive suffix, the suffix is omitted from the returned pathname. If component_name is null and the resulting pathname is longer than 168 characters, then the last 20 characters of the pathname are set to " ". If component_name is not null and the resulting archive component pathname is longer than 194 characters, then the last 20 characters of the dirname>entryname portion of the archive pathname are changed to " " and the component_name remains in the pathname. :Entry: component_check: 02/13/84 pathname_$component_check Function: This entry point is the same as pathname_$component except a status code indicates truncation instead of an invalid pathname containing "PATHNAME TOO LONG". Syntax: declare pathname_$component_check entry (char (*), char (*), char (*), char (*), fixed binary (35)); call pathname_$component_check (dirname, entryname, component_name, path, code); Arguments: dirname is the pathname of the containing directory. (Input) entryname is the entryname of the entry. (Input) component_name is the name of an archive component, or is null. (Input) path is the pathname of the entry in the given directory, or is an archive component pathname. (Output) code is a standard status code. (Output) It can be: error_table_$pathlong the pathname was truncated. Notes: If component_name is not null, the archive suffix on the entryname is optional, and is assumed if not specified. If component_name is not null and entryname ends with the archive suffix, the suffix is omitted from the returned pathname. ----------------------------------------------------------- Historical Background This edition of the Multics software materials and documentation is provided and donated to Massachusetts Institute of Technology by Group BULL including BULL HN Information Systems Inc. as a contribution to computer science knowledge. This donation is made also to give evidence of the common contributions of Massachusetts Institute of Technology, Bell Laboratories, General Electric, Honeywell Information Systems Inc., Honeywell BULL Inc., Groupe BULL and BULL HN Information Systems Inc. to the development of this operating system. Multics development was initiated by Massachusetts Institute of Technology Project MAC (1963-1970), renamed the MIT Laboratory for Computer Science and Artificial Intelligence in the mid 1970s, under the leadership of Professor Fernando Jose Corbato. Users consider that Multics provided the best software architecture for managing computer hardware properly and for executing programs. Many subsequent operating systems incorporated Multics principles. Multics was distributed in 1975 to 2000 by Group Bull in Europe , and in the U.S. by Bull HN Information Systems Inc., as successor in interest by change in name only to Honeywell Bull Inc. and Honeywell Information Systems Inc. . ----------------------------------------------------------- Permission to use, copy, modify, and distribute these programs and their documentation for any purpose and without fee is hereby granted,provided that the below copyright notice and historical background appear in all copies and that both the copyright notice and historical background and this permission notice appear in supporting documentation, and that the names of MIT, HIS, BULL or BULL HN not be used in advertising or publicity pertaining to distribution of the programs without specific prior written permission. Copyright 1972 by Massachusetts Institute of Technology and Honeywell Information Systems Inc. Copyright 2006 by BULL HN Information Systems Inc. Copyright 2006 by Bull SAS All Rights Reserved