I was refering to pathname conventions -- specificly, the path seperator should always be '/', not that of the platform where the code is running. To quote the POD (5.8.0), "In order to keep lib.pm small and simple, it only works with Unix filepaths. This doesn't mean it only works on Unix, but non-Unix users must first translate their file paths to Unix conventions." (Interestingly, this seems to increase, not decrese, the size of lib.pm -- of couse, it makes the code /using/ lib much simpiler.)

The POD is wrong at worst and misleading at best:

use lib 'd:\\foo\\bar';
use Baz;
__END__
in Baz! at d:\foo\bar/Baz.pm line 3.
Compilation failed in require at c:\temp\tlib.pl line 2.
BEGIN failed--compilation aborted at c:\temp\tlib.pl line 2.
[download]

#D:\foo\bar\baz.pm
package Baz;

die "in Baz!";
[download]

And its pretty damn stupid. How on earth to you convert a D:\foo or a \\machine\share to a "unix convention"? And is it reasonable to expect every Perl programmer to be familiar with Unix conventions?

Unix bigotry in perl really annoys me. The p5p mob should know better.


---
demerphq

_{<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...}