Re: $ENV HOME on windows
- From: Ilya Zakharevich <nospam-abuse@xxxxxxxxx>
- Date: Thu, 26 Apr 2007 15:31:49 +0000 (UTC)
[A complimentary Cc of this posting was sent to
A. Sinan Unur
<1usa@xxxxxxxxxxxxxxxxxxx>], who wrote in article <Xns991E5FEC1439Casu1cornelledu@xxxxxxxxx>:
{HOME}What puzzles me deep is why Perl on Windows is not faking $ENV
thisif $ENV{HOMEPATH} and $ENV{HOMEPATH} are both present... I think
One of these should be $ENV{HOMEDRIVE}
Yeah, thanks.
would remove at least 10-20% of porting problems...
Which might be a problem for those of us who create a D:\Home and move
users' 'My Documents' folders to directories under D:\Home\<userid> and
add a HOME variable to each user's environment. I am assuming such
problems can be avoided by checking for the existence of of $ENV{HOME}
before faking it.
Hmm, I thought that this would be clear without saying... Sorry!
However, this means that the check and the decision as
to whether to fake $ENV{HOME} should not be done at install time but
each time a script is run.
Each time the interpreter starts.
Hope this helps,
Ilya
.
- Follow-Ups:
- Re: $ENV HOME on windows
- From: A. Sinan Unur
- Re: $ENV HOME on windows
- References:
- $ENV HOME on windows
- From: Bob
- Re: $ENV HOME on windows
- From: Petr Vileta
- Re: $ENV HOME on windows
- From: anno4000
- Re: $ENV HOME on windows
- From: A. Sinan Unur
- $ENV HOME on windows
- Prev by Date: Re: Management of Enterprise Computing
- Next by Date: Re: use one subroutine's variable value in another subroutine inside a module.
- Previous by thread: Re: $ENV HOME on windows
- Next by thread: Re: $ENV HOME on windows
- Index(es):
Relevant Pages
|