Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

djberg96 (2603)

  (email not shown publicly)

Journal of djberg96 (2603)

Monday December 13, 2004
11:04 AM

Path name survey

[ #22286 ]
"A path name is-a String".

True or false?

I say "true", but I seem to be in the minority. Most folks seem not to be able to conceptually separate the *name* from the physical node on the disk.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • It has properties beyond those of a string, indicating well-formedness, existence of its target, and so on. Still, it is a string. What's the counter-argument?
    • What about UTF-8 filenames? And Unix filenames have additional restrictions: no NULL or slash characters. It may be a string, but it's probably got it's own encoding rules.


      • Yes. Those sort of well-formedness rules are the things that add to and restrict the kind of string that a path name is. An integer is a number, even though it's a restricted kind.
  • The stringiness of a path name isn't the important thing, it's the pathiness :)

    I'd say a path name should have an asString method that can represent the path name as a string (duh :), but not that it is-a string.