4.3.2 Describing the location of a program unit on the file system

4.3.2.2 Shell.File's unit-location notation

In contrast to Shell.Build, the functions in Shell.File take non-portable filenames, in the idiom of the underlying filesystem. For example, "~/MLW/basis/_text_io" on UNIX and "C:\\MLW\\basis\\_text_io" for Windows.

Note: The double backslash is necessary on Windows because a single backslash is the Standard ML way to signal an escape sequence. See the Definition.

The unit name associated with the file is deduced by comparing the file name against the entries in the source path. If the file is not in a subdirectory of an entry on the source path, then for the current compilation, the source path is extended by the directory that contains the file.

MLWorks Reference Manual (version 1.0) - 3 DEC 1996

Generated with Harlequin WebMaker