Re: "close" failing

When you are opening, printing to or closing a file you should always die. There can be things going on with a file besides you trying to write to it (for example someone deletes it while you still have it open). If you die it will tell you what it thinks is going on and gives you a hint that there may be something there that you need to look into.

Comment on Re: "close" failing

Replies are listed 'Best First'.
Re^2: "close" failing by arkturuz (Curate) on May 31, 2006 at 13:14 UTC
You don't have to `die` always. $! will tell you the error. Also, in a web app it would be nice to inform the user that something is going wrong, instead of printing 'Internal Server Error' or sth similar.	[reply] [d/l]
Re^3: "close" failing by munishdev (Initiate) on May 31, 2006 at 14:20 UTC
Another strange thing i found is that if i add ">", in front of abc.sh, it works for me. Can you tell what will ">" do to my script? open (SNMP1, ">abc.sh \|") or die "Cannot run abc.sh $!"; while (<SNMP1>) { # do some processing } close (SNMP1) or die "ERROR: testing $! $?\n ";	[reply]
Re^4: "close" failing by gellyfish (Monsignor) on May 31, 2006 at 14:26 UTC
Please use the `<code>` tags! You will find you have create a file called `abc.sh\|` in your current working directory. If you had warnings on you would also be warned about trying to read from a file handle opened for writing. /J\	[reply] [d/l] [select]


P is for Practical
	PerlMonks