It all depends on what a neater solution means. I would try to understand the functional complaint before seeking technical alternatives.

In this case, the issue is likely to be the lack of modularity of your solution, in the sense that you should be writing a logging subroutine that meets your manager's needs. Try to complete the list of requirements first, such as whether it needs a logfile naming convention (also creating required separation) to include timestamping, process identity, stage identity, file identity or whatever is functionally required. Design your own logging subroutine accordingly and get your manager to agree to it before coding it - you might find there are also site-specific requirements for how the logging routine is installed in a (site-specific) module as well as other project standards that need to be maintained.

---

---

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.