in reply to Re: When is a logical or not logical
in thread When is a logical or not logical

I like the system explaination - makes sense. Thanks for the link.

The backtick case may have been when I was still battling permissions problems. In that case I believe you are right on the mark, because without correct permissions, the command runs, but gives no output. I'll need to re-examine that now that I have those resolved.

Unfortunately that still leaves the "open" case. This one is not permissions. The curious thing is that it does create a 0 byte file, then dies. I actually had two typos in my OP. Should have been: 

open (LOGFILE, ">$logfile") or die "Can't open $logfile: $!";

[download]

Replies are listed 'Best First'.
Re: Re: Re: When is a logical or not logical
by NetWallah (Canon) on May 10, 2003 at 05:17 UTC
    Ah - well - the correction to your typo presents an explatnation not addressed yet, for the apparently anamolos behaviour. The "greater-than" symbol in the OPEN statement will be treated as an output redirect by the command prompt, even if it is inside quotes. To avoid that, it needs to be preceded by the caret (^). So, to run the open statement at the command line the way you want, you will need to enter it as: 
       open (LOGFILE, "^>$logfile") or die "Can't open $logfile: $!";

    [download]
    (Notice the tiny little "^" symbol after the first quote mark)
[reply]
[d/l]

In Section Seekers of Perl Wisdom