>> Relative paths are just more intuitive. > > For you, but not for me. > You always have to know from where the path is relative (it can be > something else than the current directory, especially if there is > "no" current directory). > > Also, relative paths going on another volume is a mystery for me.
You don't use relative paths to another volume ;) You use absolute paths into the /Volumes/ directory :) That's how I did it. I even wrote some code so that /Volumes/ works on Win32 and MacOS9 :) I actually made standard Unix paths work on all 4 platforms :) Works great. > Finally, going from a deep folder to a parent folder does not seem > the correct sense to me. It's possible. Do this ../../file.txt works in Unix and with my own path processing code :) > By analysing my thoughts, I think relative paths aren't parts of a > Mac OS 9 experienced user :-) Well they are part of Unix, and Unix is part of MacOSX for many years now. And relative paths work on MacOS9 also. You just need to write code to manage it. It's intuitive on all platforms. Anyone who uses web browsers or does HTML authoring should feel comfortable with relative paths. That's those funny things in the "href="file.html"" thing. -- http://elfdata.com/plugin/ "String processing, done right" _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
