[fs.definitions] Replace "Terms and definitions" formatting with inline definitions.

These definitions do not satisfy ISO rules for a "Terms and definitions"
section, and in any case it does not make sense for FS to have its own
"Terms and definitions". Following our usual convention, we use inline
definitions for locally-scoped terms.

Author: zygoloid

source/iostreams.tex

@@ -10006,36 +10006,41 @@
 products.
 }
 
-\rSec2[fs.definitions]{Terms and definitions}
+\rSec2[fs.definitions]{Terminology}
 
-\definition{absolute path}{fs.def.absolute.path}
-A path that unambiguously
+\pnum
+An \defn{absolute path} is a path that unambiguously
 identifies the location of a file without reference to an additional starting
 location. The elements of a path that determine if it is absolute are
 operating system dependent.
 
-\definition{directory}{fs.def.directory}
-A file within a file system that acts as a container of directory entries
+\pnum
+A \defn{directory} is
+a file within a file system that acts as a container of directory entries
 that contain information about
 other files, possibly including other directory files.
 
-\definition{file}{fs.def.file}
-An object within a file system that holds user or system data. Files can be written to, or read from, or both. A file
+\pnum
+A \defn{file} is
+an object within a file system that holds user or system data. Files can be written to, or read from, or both. A file
 has certain attributes, including type. File types include regular files
 and directories. Other types of files, such as symbolic links\iref{fs.def.symlink},
 may be supported by the implementation.
 
-\definition{file system}{fs.def.filesystem}
-A collection of files and their attributes.
+\pnum
+A \defn{file system} is
+a collection of files and their attributes.
 
-\definition{file system race}{fs.def.race}
-The condition that occurs
+\pnum
+A \defn{file system race} is
+the condition that occurs
 when multiple threads, processes, or computers interleave access and
 modification of
 the same object within a file system.
 
-\definition{filename}{fs.def.filename}
-The name of a file. Filenames \grammarterm{dot} and \grammarterm{dot-dot},
+\pnum
+A \defn{filename} is
+the name of a file. Filenames \grammarterm{dot} and \grammarterm{dot-dot},
 consisting solely of one and two period characters respectively,
 have special meaning.
 The following characteristics of filenames are operating system dependent:
@@ -10050,30 +10055,32 @@
   files, such as directories.
 \end{itemize}
 
-\definition{hard link}{fs.def.hardlink}
-A link\iref{fs.def.link} to an existing file. Some
+\pnum
+A \defn{hard link} is
+a link\iref{fs.def.link} to an existing file. Some
 file systems support multiple hard links to a file. If the last hard link to a
 file is removed, the file itself is removed.
 \begin{note} A hard link can be thought of as a shared-ownership smart
 pointer to a file.\end{note}
 
-\definition{link}{fs.def.link}
-An object that associates a filename with a file. Several links can associate names with the same file.
+\pnum
+A \defn{link} is
+an object that associates a filename with a file. Several links can associate names with the same file.
 
-\definition{native encoding}{fs.def.native.encode}
-For narrow character strings, the operating system dependent current encoding
-for pathnames\iref{fs.def.pathname}. For wide character strings, the implementation-defined execution
+\pnum
+The \defn{native encoding} of a narrow character string is
+the operating system dependent current encoding
+for pathnames\iref{fs.def.pathname}.
+The \defn{native encoding} for wide character strings is
+the implementation-defined execution
 wide-character set encoding\iref{lex.charset}.
 
-\definition{native pathname format}{fs.def.native}
-The operating system dependent pathname format accepted by the host operating system.
-
-\definition{normal form}{fs.def.normal.form}
-A path in normal form is said to be \term{normalized}.
-The process of obtaining a normalized path
-from a path that is not in normal form is called \term{normalization}.
+\pnum
+The \defn{native pathname format} is
+the operating system dependent pathname format accepted by the host operating system.
 
-Normalization of a generic format pathname means:
+\pnum
+\defnx{Normalization}{normalization!path} of a generic format pathname means:
 
 \begin{enumerate}
 \item If the path is empty, stop.
@@ -10092,52 +10099,61 @@
 \item If the path is empty, add a \grammarterm{dot}.
 \end{enumerate}
 
-\definition{operating system dependent behavior}{fs.def.osdep}
-Behavior that is dependent upon the behavior
+The result of normalization is a path in \defn{normal form},
+which is said to be \term{normalized}.
+
+\pnum
+\defnx{Operating system dependent behavior}{operating system dependent behavior} is
+behavior that is dependent upon the behavior
 and characteristics of an operating system. See~\ref{fs.conform.os}.
 
-\definition{parent directory}{fs.def.parent}
-\defncontext{of a directory} the directory that both contains a
+\pnum
+The \defn{parent directory} of a directory is
+the directory that both contains a
 directory entry for the given directory and is represented by the filename
 \grammarterm{dot-dot} in the given directory.
-
-\definition{parent directory}{fs.def.parent.other}
-\defncontext{of other types of files} a directory containing a directory
+The \defn{parent directory}
+of other types of files is a directory containing a directory
 entry for the file under discussion.
 
-\definition{path}{fs.def.path}
-A sequence of elements that identify
+\pnum
+A \defn{path} is
+a sequence of elements that identify
 the location of a file within a filesystem.
 The elements are the
 \grammarterm{root-name}\opt{},
 \grammarterm{root-directory}\opt{},
 and an optional sequence of filenames.
 The maximum number of elements in the sequence is operating system dependent.
 
-\definition{pathname}{fs.def.pathname}
-A character string that represents the name of a path. Pathnames are
+\pnum
+A \defn{pathname} is
+a character string that represents the name of a path. Pathnames are
 formatted according to the generic pathname format grammar\iref{fs.path.generic} or an
 operating system dependent
 native pathname format.
 
-\definition{pathname resolution}{fs.def.pathres}
-Pathname resolution is the operating system dependent mechanism for resolving
+\pnum
+\defnx{Pathname resolution}{pathname resolution}
+is the operating system dependent mechanism for resolving
 a pathname to a particular file in a file hierarchy. There may be multiple
 pathnames that resolve to the same file.
 \begin{example} POSIX specifies the mechanism in section 4.11, Pathname resolution.
 \end{example}
 
-\definition{relative path}{fs.def.rel.path}
-A path that is not absolute, and as such, only unambiguously
+\pnum
+A \defn{relative path} is
+a path that is not absolute, and as such, only unambiguously
 identifies the location of a file when resolved\iref{fs.def.pathres} relative to
 an implied starting location. The elements of a path that determine if it is
 relative are operating system dependent.
 \begin{note}
 Pathnames ``.'' and ``..'' are relative paths.
 \end{note}
 
-\definition{symbolic link}{fs.def.symlink}
-A type of file with the
+\pnum
+A \defn{symbolic link} is
+a type of file with the
 property that when the file is encountered during pathname resolution, a string
 stored by the file is used to modify the pathname resolution.
 \begin{note} Symbolic links are often called symlinks. A symbolic link can be thought of as a raw pointer to a file.