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.
#D:\foo\bar\baz.pm package Baz; die "in Baz!";

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...

In reply to Re: Re: Re: When in Rome: Re: colons don't always separate path items! by demerphq
in thread colons don't always separate path items! by John M. Dlugosz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.