On Fri, Jul 07, 2000 at 10:40:19AM +0200, Vincent Lefevre wrote:
> On Thu, Jul 06, 2000 at 13:28:19 +0100, Richard Proctor wrote:
> > I think it would be better if perl did not need the file names to
> > have the "/pm" in the name, but used the basic name, or possibly a
> > file type, as alternitives.
>
> But there could be name conflicts (this has already happen with an
> old version of Perl, when the /pm wasn't needed). If your disc format
> doesn't support long names, you can use raFS; this is what I do.
There was certainly a conflict between .pm and .bs which sent dynaloaded modules
into a spin.
A solution which allowed the /pm to be shaved would only help modules with names
of 8 to 10 characters. Above that you're still going to hit the problem of
use MyLongModule;
being happy with the file "MyLongModu" on a 10 character truncating filesystem
because perl is asking for the file "MyLongModule" but the *filesystem* is doing the
truncation and match, but when it's copied to a long filename system (RISC OS 4
filecore, NFS, raFS) it will retain the name "MyLongModu", which the long filename
system will not consider a match for "MyLongModule"
Personally it would seem safer if you're making the transition to a long name system
to use a script to take each file and look for
/package\s+[A-Za-z_0-9:]*([A-Za-z_0-9]+);/ and name the file "$1/pm"
(with a backup copy of your tree in case things go wrong)
Nick
