That's all very well, but if the file/dir string passed to unlink/rmtree simply doesn't exist or script does not have sufficient rights to perform the deletion, the will be neither a compilation error nor a run-time exception raised. I know cos I tried both situations. Therefore $@ will never be set, so neither failure will be detected.
$! is set in both cases.
I therefore can see no benefit in evaling these calls to functions. Better to use the standard idiom of unlink $file or die/warn/LOG $!; and rmtree $dir or die/warn/LOG $!; don't you think?
Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.
In reply to Re: Re: Re: My first thought was to build a macro... was I right?
by BrowserUk
in thread My first thought was to build a macro... was I right?
by princepawn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |