L
Lew Pitcher
Derk Gwen wrote:
[snip]
<supplementary>
FWIW, the IBM C-Set compiler accepts filename strings in the form of
"A.B.C.D" for access to the file named A.B.C.D
and
"DD
DNAME" for access to the JCL DD named DDNAME, which will contain an
indirection to the /real/ name of the file (//DDNAME DD DSN=A.B.C.D )
The C standard doesn't define /how/ the filesystems are to interpret the name
given to fopen(), and a filename that's legal on one system may be completely
illegal on another.
</supplementary>
--
Lew Pitcher
Master Codewright and JOAT-in-training
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
[snip]
What is outside the C standard is how the string in the fopen is used to
identify the data source, and what steps are necessary to make the source
available. There's no particular reason why a standard C library could not
(or could) accept something like "ftp://saturn/development/quark.tcl".
<supplementary>
FWIW, the IBM C-Set compiler accepts filename strings in the form of
"A.B.C.D" for access to the file named A.B.C.D
and
"DD
indirection to the /real/ name of the file (//DDNAME DD DSN=A.B.C.D )
The C standard doesn't define /how/ the filesystems are to interpret the name
given to fopen(), and a filename that's legal on one system may be completely
illegal on another.
</supplementary>
--
Lew Pitcher
Master Codewright and JOAT-in-training
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.