Re: $! after using backticks

2001-05-23 Thread Randal L. Schwartz
> "Timothy" == Timothy Kimball <[EMAIL PROTECTED]> writes: Timothy> As for always getting that weird error message from $!, I always Timothy> get "Illegal seek" on my machine. You should never look at $! unless immediately following a *failed* system-related call. A successful call doesn't

RE: $! after using backticks

2001-05-23 Thread Mitchell, Ronald
ris and Windows.) Thanks again - I'd been struggling with this for ages. (And thanks to the others who've replied as I've been typing this!) Ron -Original Message- From: Peter Cornelius [mailto:[EMAIL PROTECTED]] Sent: 23 May 2001 19:14 To: 'Mitchell, Ronald'; '[

Re: $! after using backticks

2001-05-23 Thread Me
Enter: perldoc perlvar and then look at the entries for $CHILD_ERROR ($?) and $ERRNO ($!). There can be other issues about return values, but start with the above.

Re: $! after using backticks

2001-05-23 Thread Timothy Kimball
Ron Mitchell wrote: : I want to check that a backtick command has executed OK. I thought I could : do that by looking at the $! variable. Check $? instead. This one's for pipes, backticks, & system() commands. It's a fairly complex flag, with a lot of stuff in it, but briefly, $? >> 8 contains t

RE: $! after using backticks

2001-05-23 Thread Peter Cornelius
>I want to check that a backtick command has executed OK. I thought I could >do that by looking at the $! variable. Check $? This is Child exit status which is what you get when you spawn another process with back ticks. The $! is the ERRNO (or Error string depending on context) for the last sy