This seems like a good idea. I'd like to know a little more though:

• How does the synopsis section of the POD look?
• Is it compatible with non-Exporter.pm exporters?
• Do you trace only subroutines?
• How is the actual tracing done?

I think that if you're going to release this to CPAN, you should put some extra thought into making it potentially useful not just for the task your doing, but also other similar tasks, without making the original idea any less convenient. In fact, I think you shouldn't implement anything you don't need, but design so that it's easy to add and put a comment in the documentation saying that you're open to suggestions and patches.

A synopsis and a brief summary of the implementation would really help.

lodin

---

---

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.