Thanks Tom, it helped. :-)
I learned some more few things. ;-)
Regards,
Tom Phoenix <[EMAIL PROTECTED]> wrote:
On Dec 30, 2007 10:17 AM, oscar gil wrote:
> What I still don't understand is why $! and $^E are set as there was an
> error though there was not :-?.
Those variables may
On Dec 30, 2007 10:17 AM, oscar gil <[EMAIL PROTECTED]> wrote:
> What I still don't understand is why $! and $^E are set as there was an
> error though there was not :-?.
Those variables may be set when your perl binary internally needs to
use a system call or something similar. During or shortly
On Dec 29, 2007 9:18 AM, oscar gil <[EMAIL PROTECTED]> wrote:
> Using 'open' I cannot say if the 'del' command was done correctly
> or not, although there is a message probably to STDERR that I do
> not know how to manage. :-(
I believe you're talking about a piped open() to an external command
Thanks John for your quick answer.
what you said about:
>Only the $? variable applies to the system() function. I think that
>'del' is an internal command.com function (I haven't used DOS/Windows
>in a long time) so $? will probably report the return status of
> command.com?
...
oscar gil wrote:
Hello everybody,
Hello,
I wanted to learn a bit more about how to handle errors when I am
working with files,
Do you want to handle errors or do you want to report errors?
so I wrote this simple script to start with it
where you can see that first I show the normal perl e
