If all you have is the filename and reason of failure then you might spend hours trying to find out why the heck did you try to open the file at all. The unability to open a file doesn't have to be an administration problem, a permissions issue or something similar. You migth have an error somewhere in the code that generates the filename and then it might be very helpfull to be able to tell which open statement failed.

OTOH, it may be good to display only the "basic" stuff to the user and log the details into a file. Sometimes this is not possible and then it may be fine to include information that will be useless to the user directly, but may come in handy when the user calls that he just got an error that something went wrong on some silly line 12345.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.