I extend my perl module path with PERLLIB in my environment... is PAR smart enough to pick that up?
I can't speak definitively, but it appears so (PAR isn't being smart, and this may be a bug) 

C:\dev\LOOSE>cat par.inc.t

print "
here are the \@INC buddy
@INC

";



C:\dev\LOOSE>perl par.inc.t

here are the @INC buddy
honk C:/Perl/lib C:/Perl/site/lib .


C:\dev\LOOSE>pp par.inc.t

C:\dev\LOOSE>a.exe

here are the @INC buddy
CODE(0x12e317c) honk .


C:\dev\LOOSE>

[download]

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: Re: PAR, commandline args, WinXP by PodMaster
in thread PAR, commandline args, WinXP by rkg

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.