|
Well, I mean, it frequently lies between the name and the extension, though it can also lie within the name on some systems. Of course in OpenVMS it also lies within the directory path as well.
Not very trustworthy, those dots.
|
|
|
|
|
Extension includes the dot, as demonstrated by this PowerShell sample
New-Item test.txt -ItemType File | Select-Object -ExpandProperty Extension
which returns .txt, with the dot
^Priscilla
|
|
|
|
|
Exactly!
It is called dotnet and not net!
|
|
|
|
|
Which doesn't answer the question.
|
|
|
|
|
Which is also why I voted that it is part of the extension. While you could argue that it's a delimiter (and I'd be ok with that) a file without an extension doesn't have a .
E.g. MyFile vs MyFile.txt
|
|
|
|
|
A directory name doesn't have a \ at the end, either.
So therefore, the \ that you have to add before a subdirectory is not a delimiter, is that right?
The \ is part of the subdirectory name, right?
If we had a file system without extensions, but related files were collected in a directory, e.g.
...\myprogram\h (for the declarations)
...\myprogram\c (for the active statement code)
...\myprogram\obj (for the compiled object code)
...\myprogram\exe (for the linked executable)
then the separating slashes are delimiters, and not part of neither directory nor file name - right? But if we have two separate name parts in the same file name descriptor (as in FAT), externally separated by a dot, like
...\myprogram.h (for the declarations)
...\myprogram.c (for the active statement code)
...\myprogram.obj (for the compiled object code)
...\myprogram.exe (for the linked executable)
then the separator is not a delimiter, and we make an arbitrary decision to associate it with the second name part, part of the extension?
You can take it one step further: Named (alternate) streams. ...\dir\Myfile.txt:stream2 - is the colon part of the stream name, similar to the dot being part of the extension? The slashes and colon are not part of any name part, while the dot is part of the extension name part? That appears rather random, arbitrary - doesn't it?`
In a *nix filesystem with no real concept of an 'extension', it makes sort of sense, except that it makes less sense to extract part of a name and call it 'extension'. In FAT, it is different. In NTFS, it is mixed.
So my answer to the question is 'Can't tell!' - but that is not one of the options.
|
|
|
|
|
The question: Your personal opinion, not "what my framework says".
|
|
|
|
|
...to be more exact in today's possibilities for filenames:
the LAST "." in a filename is the delimiter between filename and extension.
it is not part of the extension and not part of the filename. it's a delimiter.
|
|
|
|
|
With today's capabilities and technical language, we might even say that each part delimited by a dot excluding the first is a tag. The last tag is customarily used to determine the correct application to interprete that file's contents.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|