well, it would probably involve some parsing not sure how you want to solve
that, but try running this on your box:
for (keys %ENV) { print "$_ has value $ENV{$_}\n" }
# this will print out all ENV key/values for you
$ENV{PATH} has the following contents on my machine:
C:\winnt\system32;C:\winnt;C:\winnt\system32\WBEM;C:\Perl\bin\;C:\PROGRA~1\U
LTRAE~1;E:\mysql\bin
so if perl is in your path, you can tell your machine where it is...
now, if you cant parse it, you could of course add a special temp folder or
something pointing at your perl path and use *that*
but it's perl that uses %ENV and i think you'll find yourself in a catch22
;-)
Regards,
Jos Boumans
> I'm writing perl scripts that will be distributed to locations where I
> cannot gaurantee the location of perl. Is there a clean alternative to the
> shebang with the specific perl path? Maybe using an environment variable
to
> locate perl?
