Dan Sugalski wrote:
> > >+(note the trailing period in the definition of PERLSRC). Perl modules
> > >+from CPAN can be just as bad (or worse), so watch out for them, too. The
> > > configuration script will warn if it thinks you're too deep (at least on
> > >-versions of VMS prior to 7.2).
> > >+versions of VMS prior to 7.2). But MakeMaker will not warn you if you
> > >+start out building a module too deep in an ODS-2 directory.
> >
> >This might be where I got the wrong idea in the first place, although I'm
> >quite capapble of coming up with the wrong idea on my own ;-). In any
> >case, good work, Peter.
>
> That's something we should probably fix to say something about VAXen and
> Alpha VMS versions before 7.2.
OK, as Dan showed his ODS-2 devices go deep and a paragraph from the
URL that Craig mentioned reads:
B.2.1.3 Deeply Nested Directory Support
Under Extended File Specifications on Alpha, RMS supports deep nesting of
up to 255 directories, with the restriction that the total
directory specification must be no longer than 512 8-bit or 16-bit
characters. The deep nesting of directories is also supported on
ODS-2 disks.
However I would like to stop short of saying something like "VAXes - even
ones running 7.2 cannot go deep" since I asked on comp.os.vms about whether
they could and got no definitive response (Arne V. was not sure). If it
turns out that they do not we'll have to toss an f$getsyi("ARCH_NAME") into
the VMS version check in configure.com but that should not be too difficult.
Peter Prymmer
P.S. I intend to update Craig's email address as listed in README.vms too.
I just missed that one yesterday :-)
