Yes, in *NIX land.
I'll take your word for that as I know next to nothing about *nix.
On the other hand I've used and programmed every version of NT since 3.51 except 7 and rt.
If, however, all I do is fire up the Environment Variable dialog ...
That dialog is a part of the windows graphical shell. The alternative shell to cmd.exe.
After you've used that dialog and the %perl_path% has been expanded, check the path variable in the registry. It will no longer contain %perl_path%; it will have been replaced by the expansion.
So why not just put the directories into the path variable to start with?
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
Because I expect to change the Perl version on a regular basis and I don't want to have to parse PATH to do it.
| [reply] |
Because I expect to change the Perl version on a regular basis and I don't want to have to parse PATH to do it.
Then don't. Just install each new version into the same place -- say X:\perl or wherever -- and then you have no need to change or edit or parse the path.
Or, if that is too simple, install new builds into versioned directories and then use:
subst p: X:\path\to\latest\version\of\perl\bin
And have p:\ in your path.
There are many ways to achieve what you want; stop trying to use the one that won't.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply]
[d/l]
[select] |