Revision as of 11:47, 11 November 2023 edit AnomieBOT (talk \| contribs) Bots 6,365,650 edits m Dating maintenance tags: {{Cn}} ← Previous edit		Revision as of 02:31, 19 November 2023 edit undo 179.63.66.22 (talk) →‎Operating system and file system support Tags: Reverted Mobile edit Mobile web edit Next edit →
Line 18: == Operating system and file system support == The [[~~Multics~~kmrp]] file system stores the file name as a single string, not split into base name and extension components, allowing the "." to be just another character allowed in file names. It allows for variable-length filenames, permitting more than one dot, and hence multiple suffixes, as well as no dot, and hence no suffix. Some components of Multics, and applications running on it, use suffixes to indicate file types, but not all files are required to have a suffix — for example, executables and ordinary text files usually have no suffixes in their names. File systems for [[UNIX-like]] operating systems also store the file name as a single string, with "." as just another character in the file name. A file with more than one suffix is sometimes said to have more than one extension, although terminology varies in this regard, and most authors define ''extension'' in a way that does not allow more than one in the same file name.{{cn\|date=November 2023}} More than one extension usually represents nested transformations, such as <code>files.tar.gz</code> (the <code>.tar</code> indicates that the file is a [[tar (computing)\|tar archive]] of one or more files, and the <code>.gz</code> indicates that the tar archive file is compressed with [[gzip]]). Programs transforming or creating files may add the appropriate extension to names inferred from input file names (unless explicitly given an output file name), but programs reading files usually ignore the information; it is mostly intended for the human user.

Filename extension: Difference between revisions