Arrows by any other name
-
_Maxxx_ wrote:
e.g. C:\Folder\Directory\myFile.txt
Path
_Maxxx_ wrote:
e.g. myFile.txt
File or filename
_Maxxx_ wrote:
e.g. C:\Folder\Directory
Folder or directory
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
Kornfeld Eliyahu Peter wrote:
Folder or directory
A good example of nuance I've never really gotten.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
-
Kornfeld Eliyahu Peter wrote:
Folder or directory
A good example of nuance I've never really gotten.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
Originally folder is a logical term where used much before computers, where directory is the physical place on the storage and came to use with computers...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
what do you call a sting that holds a file path together with the file name itself e.g. C:\Folder\Directory\myFile.txt And what do you call just the file name? e.g. myFile.txt And what about just the name of the folder the file is in? e.g. C:\Folder\Directory I never seem to be consistent - I think we need a new word (or am I missing something?)
You forgot relative path, for example: ./bin/debug Marc
-
Filepath:C:\Folder\Directory\myFile.txtFilename:myFile.txtFolderpath, or path:C:\Folder\DirectoryFolderDirectory~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
Rage wrote:
Filename:
myFile.txtI would change that slightly:
FileName:myFileComplete Filename:myFile.txtThose who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
what do you call a sting that holds a file path together with the file name itself e.g. C:\Folder\Directory\myFile.txt And what do you call just the file name? e.g. myFile.txt And what about just the name of the folder the file is in? e.g. C:\Folder\Directory I never seem to be consistent - I think we need a new word (or am I missing something?)
_Maxxx_ wrote:
And what about just the name of the folder the file is in?
They aren't folders they are directories. It should still be called FileManager, not Windows' Explorer. A pox upon whoever made those UI decision.
-
Kornfeld Eliyahu Peter wrote:
Folder or directory
A good example of nuance I've never really gotten.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
There is no folder; only directories.
You'll never get very far if all you do is follow instructions.
-
what do you call a sting that holds a file path together with the file name itself e.g. C:\Folder\Directory\myFile.txt And what do you call just the file name? e.g. myFile.txt And what about just the name of the folder the file is in? e.g. C:\Folder\Directory I never seem to be consistent - I think we need a new word (or am I missing something?)
In my code, filename means just the filename (and extension); pathname means the entire path including filename. The path is just the path.
-
_Maxxx_ wrote:
C:\Folder\Directory\myFile.txt
filename
_Maxxx_ wrote:
myFile.txt
filename
_Maxxx_ wrote:
C:\Folder\Directory
path The first two are basically the same thing: both of them let you find a file. One is relative and one is absolute but in most cases you don't care about that. I/O methods will accept either and do the right thing. If you do care then I'd call the first either filePath or absoluteFilename.
-
_Maxxx_ wrote:
And what about just the name of the folder the file is in?
They aren't folders they are directories. It should still be called FileManager, not Windows' Explorer. A pox upon whoever made those UI decision.
Absolutely. Directories are EXACTLY right, as the directory is jsut a collection of pointers to the files within - whereas the folder metaphor implies the physical existence of the files within the folder, which is drivel and rot. If anything, a disk drive should be a folder, containing directories of files. But we are victims of the dumbing down of It and, in most cases, it doesn't matter to the user who (lets be honest) call their monitor their computer and the computer their hard drive!
-
Absolutely. Directories are EXACTLY right, as the directory is jsut a collection of pointers to the files within - whereas the folder metaphor implies the physical existence of the files within the folder, which is drivel and rot. If anything, a disk drive should be a folder, containing directories of files. But we are victims of the dumbing down of It and, in most cases, it doesn't matter to the user who (lets be honest) call their monitor their computer and the computer their hard drive!
Exactly! Also More Like An Index Or Catalog. A Document May have links From Many Directories. Try That With Folders!!
You'll never get very far if all you do is follow instructions.
-
what do you call a sting that holds a file path together with the file name itself e.g. C:\Folder\Directory\myFile.txt And what do you call just the file name? e.g. myFile.txt And what about just the name of the folder the file is in? e.g. C:\Folder\Directory I never seem to be consistent - I think we need a new word (or am I missing something?)
-
what do you call a sting that holds a file path together with the file name itself e.g. C:\Folder\Directory\myFile.txt And what do you call just the file name? e.g. myFile.txt And what about just the name of the folder the file is in? e.g. C:\Folder\Directory I never seem to be consistent - I think we need a new word (or am I missing something?)
pfn - i.e. path file name fn - file name path Examples from function/method declarations:
std::string slurp(const std::string aPfn); void A::B::startApp(const char\* app\_fn); // activate threads void Filter(std::string a\_localAppPfn, // argv\[0\] - where app resides on this system std::string a\_peerAppPfn, // argv\[1\] - where to store app on peer system
