|
Make it so.
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
If I type three dots, MS Word changes them into an ellipsis, represented as a single character. Is then the first, or rather, the first third of this character part of the extension? But then, what about the second and third part? They must be equal parts of the extension, too, otherwise things will be messed up completely!
Or maybe only the last point of the ellipsis is part of the extension, so that the ellipsis character is two thirds file name and one third extension ...
But you said four dots! Then comes the question of which three dots make up the ellipsis. If you just keep on typing four dots, the first three may be interpreted as an ellipsis and the last one considered 'independent'. But if you go back for later editing, positioning the cursor between the last name (/word) and insert another dot before the ellipsis, then maybe that dot plus two thirds of the ellipsis belongs to the file name, while the third third of the ellipsis belongs to the extension.
I guess that some fonts will render an ellipsis in a way that so that it can be distinguished from solitary dots. This doesn't change the problem, though: Can a third of a character be part of a file extension?
|
|
|
|
|
|
Same with the slash in file paths: Is it part of the preceding directory name or of the following directory or file name?
In USA, it is quite common to refer to people by first name, middle initial with a dot, and last name, such as 'Franklin W. Dixon'. Is the dot part of the middle name? Of the middle initial?
|
|
|
|
|
|
When people talk about file extensions, they say things like "dot x l s x" as frequently as not. Also, in Windows, the last dot in the full filename isn't shown when Explorer is hiding extensions.
|
|
|
|
|
|
According to C++ std::filesystem::path::extension it is
|
|
|
|
|
And C++ is the ruler of all OSes and all languages.
|
|
|
|
|
|
Which doesn't answer the question.
|
|
|
|
|
See title
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
It depends on the OS you'd be using, what purpose you're looking at it for, and so on.
So I don't care.
Now, if you argument about something important let's talk about "How do you pronounce 'gif'?" and we'll have a holy war!
|
|
|
|
|
Peter Kelley 2021 wrote: let's talk about "How do you pronounce 'gif'?" and we'll have a holy war! Pfff... nothing comparable to the "brackets in a dedicated line"
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Nelek wrote: brackets
< > = beaks
[ ] = square
{ } = curly
( ) = roundy
I hope I've cleared it all up. 
|
|
|
|
|
Yes, you did.
Thank you, nitpicky
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
It is part of the extension because you cannot have a file name with a DOT that does not have an extension windows will remove the DOT if you try to use it without an extension (you cannot have "filename.") so not part of the name. Now I need more Coffee 
|
|
|
|
|
It's a delimiter, most of the time. It's meant to separate the filename and the extension.
|
|
|
|
|
See title.
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Even if the underlaying file system is a *nix style one?
|
|
|
|
|
That hits the dot. It's a delimiter.
But, If we look at it strictly and take it more precisely, linux file systems don't has file extensions and such definition!
Something about which we often break our head:
"In the name of the Compiler, the Stack, and the Bug-Free Code. Amen."
(source unknown)
|
|
|
|
|
I have had to consider it in both ways depending on what I have programmed. So I don't really care about the "definition".
When I need to interact with filenames, I just do a first test, check if it "is part" or not and then end the function according to the result.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
But that doesn't answer the question.
|
|
|
|
|
I think the "I don't care" subject line is a rather unambiguous choice among the answer alternatives provided.
|
|
|
|
|
I wasn't commenting on his subject line.
|
|
|
|