Maybe this web page might help:
https://en.wikipedia.org/wiki/Path_(computing)
There is a sentence here which says: "An absolute or full path points to the
same location in a file system..."
so I conclude that an absolute or full path is one and the same thing. That
should answer
the first question.
To clarify my question (in #2), consider this example:
Assume you are in a directory called C:\sim and there are a bunch of
subdirectories in there
with project names. To change into one of those subdirectories you can type at
the command
prompt:
cd project1
cd .\project1
both of which will put you into the "project1" directory. I wonder which of
these are
allowed according to our spec. I think both should be, but I am not sure
whether we
have any rules about how this relative path should be spelled.
Here is another example for the absolute path situation. Let's assume you are
in a
directory deep down in your tree, and then you type the following:
cd \sim\project1
cd C:\sim\project1
They will both take you into the "project1" directory, no matter where you are
on the tree.
Interestingly, the second line will still work even if you are on another
drive. For
example, on the C: drive, put yourself into the c:\sim\project1 directory, then
change
drives to, say d:, and from the d: drive type cd C:\sim. The command prompt
will still
show you d:, but if you now go back to drive c:, you will be in C:\sim.
Anyway, currently we don't allow the path to contain C:\ (or \\), but I wonder
whether
we do allow \ or .\ at the beginning of a path. It seems that we don't say
anything on
that, and I think we should. Similarly, since
\sim\project1
C:\sim\project1
are both "absolute paths", are we trying to disallow absolute paths all
together, or
just the drive letter and network path references? I am just looking for a
little more
consistency and clarity in this regard.
Thanks,
Arpad
============================================================================================
From: ibis-editorial-bounce@xxxxxxxxxxxxx
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Mirmak, Michael
Sent: Wednesday, April 26, 2017 3:12 PM
To: ibis-editorial@xxxxxxxxxxxxx; ibis-interconn@xxxxxxxxxxxxx
Subject: [ibis-editorial] BIRD186.3 draft 6
After discussions in today's IBIS Interconnect Task Group and on-line, I am
enclosing a draft 6 version of BIRD186.3. The changes in this draft are based
on Bob Ross's draft 5 document circulated earlier this week. Most of the
changes simply clarify which text is being changed for future editorial work,
but there are some additions to the Chapter 3 material that should receive
close scrutiny.
Two key points remain to be settled:
1) There is an unclear distinction in this draft between "full path name"
and "absolute path name". Additional examples would help our development of
the final text, as well as reader understanding.
2) Per a point raised by Arpad Muranyi, there is no clear statement here
as to whether relative paths featuring ./ or .\ are permitted. Further, while
\\ and C:\ are prohibited for absolute paths, there is no clear statement
regarding whether / is permitted or not.
Comments and discussion are welcome and encouraged. Thank you.
- MM
