Here's a list of attributes that I found in my old Symbolics Reference
Guide to Streams, FIles, and I/O. (March 1985)
Host
Device
Directory
Name
Type
Version
Plus it needs to handle cross-system support. How to specify the name
of a unix file when running on a VMS system.
A few of the features, I found while skimming through the document.
Wildcard conventions, relative directories, os dependent naming
conventions.
<chaim>
>>>>> "NW" == Nathan Wiger <[EMAIL PROTECTED]> writes:
NW> Here's an idea. Our new nifty fileobjects ($fo) could have some "jars"
NW> where path info is stuck internally automatically. We could have methods
NW> for:
NW> $fo->pathdrive # Windows drive
NW> $fo->patharray # array of split-up filename
NW> $fo->pathdelim # / or \ or :: or ?????
NW> So trace this call:
NW> $fo = open "C:\Windows\System\IOSUBSYS\RMM.PDR";
NW> $fo->pathdrive = "C:" ;
NW> $fo->patharray = [ Windows, System, IOSUBSYS, RMM.PDR ];
NW> $fo->pathdelim = "\";
NW> So, this would be the internal representation of the filename. A UNIX
NW> one would be similar, it's just that the drive jar would be empty:
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
