Under ITS I think they were just separated by a space
On 8/18/2026 5:57 AM, anthk@not.dev.null wrote:
Under ITS I think they were just separated by a space
The "dot separator" is just the full-stop
symbol in english language, or the decimal
point in mathematics.
In Unix/Linux filesystems, that is so. But before that became
ubiquitous, the parts of the filesystem were separate fixed-length
fields in the file directory entries, and the separators were not in the
file directory, but were added as syntactic sweeteners in the command language and the display routines.
According to Mr. Chang Man-wai <toylet.toylet@gmail.com>:
But in the naming method,
which is the file name?
Which is the file name extension? :)
I think the question doesn't make sense. The reason computer files have extensions is to describe the format of the contents: text, executables, spreadsheet, whatever. That makes it a lot easier to select the appropriate software to process them. Microsoft famously got this wrong, by looking at the contents of the file to decide how to process it instead of the name, so you can have a mail attachment called CONTRACT.TXT which is in fact an executable full of malware.
In paper files, it's generally obvious what kind of material is in the folder, or if it's not, it doesn't matter since there's only one way to process it, pull out the file and look at it.
John Levine-a scribbled something on Tuesday the 8/25/2026:
According to Mr. Chang Man-wai <toylet.toylet@gmail.com>:
(crossposting put on a diet)
But in the naming method,
which is the file name?
Which is the file name extension? :)
By convention, a computer filename is the whole string identifying the
file, but can also be used to describe the substring that is everything
up to the extension (and its separator).-a The extension is everything
after the last separator.-a In MSDOS days ... and other simple file systems,-a like the CP/M ancestor of FAT ... the extension was the 3 characters that fit into the directory entry structure field labeled "extension".
I think the question doesn't make sense. The reason computer files have
extensions is to describe the format of the contents: text, executables,
spreadsheet, whatever. That makes it a lot easier to select the
appropriate
software to process them. Microsoft famously got this wrong, by
looking at the contents of the file to decide how to process it
instead of the name, so you can have a mail attachment called
CONTRACT.TXT which is in fact an executable full of malware.
I don't think this is what Microsoft did.-a Unix is the OS that uses
"magic" (special bytes at offset 0) to decode what a file is ... you can specify which shell is to execute a script, for instance.-a (Linux has
also adpted this technique.)
Microsoft is famous for trying to open a binary file in a text editor because it has a .txt extension.
In paper files, it's generally obvious what kind of material is in the
folder, or if it's not, it doesn't matter since there's only one way to
process it, pull out the file and look at it.
There are plenty of situations where a librarian is dependent on a
subject matter expert to identify what a book or paper file is.-a And
they may need help to identiify which expert is needed.
/dps
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 56:30:50 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,806 |