Arrows by any other name

[Mohamad M Mohamad]

This is good :thumbsup:

[BobJanova]

_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.

[Rage]

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]

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)

[Marc Clifton]

You forgot relative path, for example: ./bin/debug Marc

[OriginalGriff]

Rage wrote:

Filename:
myFile.txt

I would change that slightly: FileName: myFile Complete Filename: myFile.txt

Those 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 – ∞)

[MarkTJohnson]

_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.

[PIEBALDconsult]

There is no folder; only directories.

You'll never get very far if all you do is follow instructions.

[Joe Woodbury]

In my code, filename means just the filename (and extension); pathname means the entire path including filename. The path is just the path.

[Lost User]

BobJanova wrote:

he first two are basically the same thing

Nonsense

BobJanova wrote:

I/O methods will accept either and do the right thing

Lordy lord, what sort of systems are you working on?

[Lost User]

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!

[PIEBALDconsult]

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.

[Lost User]

You call them all a path. Then you have methods to tell you which bits they include. Look at the dot net System.IO.Path namespace. If you can work the word 'Rooted' in there somewhere you are doing really well.

[DOUGLAS O MOEN]

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