Re: PAR, commandline args, WinXP

Perhaps noteworthy:

I extend my perl module path with PERLLIB in my environment... is PAR smart enough to pick that up?
I have a BEGIN block that looks at @INC and modifies some constants based on the directory structure it discovers there... could that be clashing with PAR?

Comment on Re: PAR, commandline args, WinXP

Replies are listed 'Best First'.

Re: Re: PAR, commandline args, WinXP
by PodMaster (Abbot) on Nov 16, 2003 at 20:45 UTC

I extend my perl module path with PERLLIB in my environment... is PAR smart enough to pick that up?


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.

[reply]
[d/l]

Re: Re: Re: PAR, commandline args, WinXP

by chromatic (Archbishop) on Nov 17, 2003 at 01:28 UTC

PAR works by putting a code reference at the start of @INC. Putting something else there (through environment variables) may indeed cause problems.

[reply]
[d/l]