On Tue, Oct 21, 2008 at 03:07:41PM -0500, Ken Williams wrote:
> On Mon, Oct 20, 2008 at 9:26 AM, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> > On Mon, Oct 20, 2008 at 02:25:55PM +0100, Nicholas Clark wrote:
> >>
> >> $ ./perl -le 'print "$^X on $^O"'
> >> /home/nick/p4perl/perl/perl on linux
> >>
> >> $ ./perl -le 'print "$^X on $^O"'
> >> ./perl on freebsd
>
> Unfortunately there's also the behavior when $PATH is searched:
>
> $ perl -le 'print "$^X on $^O"'
> perl on darwin
>
> Perhaps we should only transform to an absolute path when it contains
> one or more slashes?
Safer would be on if -x $^X, as that copes with people who have . in $PATH.
But I double checked, and the patch was only active inside a block where
$ENV{PERL} is true, so it's only going to apply to people testing with an
uninstalled fresh perl, so in the cases where it triggers they're not going
to be invoking perl from $PATH.
Nicholas Clark
