«

On 3 Aug 2004 11:44:41 GMT, Julius Plenz <> wrote:

>> I tried $ENV{HOME}/x.pl also, but it also gave the same error :
>
>Did you also try "$ENV{HOME}/x.pl"?

He means that he tried writing that ON STDIN, not literally in the
program source...


Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"

Here's another thought. If you want true shell-like evaluation, you could
literally pass your input to the shell.

> my $fileToCheck = <STDIN>;

$fileToCheck=`echo $fileToCheck`;

> chomp ($fileToCheck);
> if (-e $fileToCheck)
> {
> print "Not Found\n";
> }

This should expand "~" as well as expand environment variables and do other
shell things. However, this is kind of quick and dirty. Not as safe as

$fileToCheck =~ s/\$(\w+)/$ENV{ $1}/g;


>
> The problem is that I want to allow the user to specify the file with
> environment variables in some way. For example, to check if x.pl is
present
> under the home directory, the user should be able to give
>
> $HOME/x.pl
>
> However, it seems that we cannot interpolate like this while reading from
> STDIN (or from a file)? Am I missing something ?
>
> I tried $ENV{HOME}/x.pl also, but it also gave the same error :
>
> No such file or directory
>
> TIA
>
> --
> Abhinav