On Mon, Mar 19, 2001 at 10:17:15AM -0800, Peter Prymmer wrote:
>
> On Sun, 18 Mar 2001, Craig A. Berry wrote:
>
> > There are two problems here, one the double slash before "build,"
> > which I assume would be a problem even on Unix, and the other is the
> > extremely long directory name. The most common volume format on VMS
> > has a limit of 39.39, but I believe Perl also supports 8.3 and 14.3
> > filesystems which would run into trouble far sooner. For creating
> > temporary directory names portably you might consider using
> > File::Temp, where the porting work has already been done.
>
> As a practical matter the double slash may not be a problem on most
> contemporary commercial unixes including linux and *BSD, but of course
> Perl is supposed to work even on older/odder unixes. The two file systems
> that I know where // is definitely a problem are Mach Ten running on Mac
> OS and Unix Systems services on OS/390. In the former case a _leading_ //
> indicates acess to a Mac OS file and in the latter case a _leading_ //
> indicates a path to an MVS legacy data set (hence at least for OS/390 a
> // in the middle of a filepath should pose no problem but it's use is
> highly discouraged).
A third one is the Apollo Domain/OS (pretty rare these days,
admittedly, but still not gone) filesystem. Basically, a leading //
indicates a network filesystem, //foo indicates data living in the
cluster node foo, IIRC.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
