What you request is non-standard behavior, hence no module should ever automatically "bubble up" two caller levels to the "grandparent" *

It's the module in the middle which could use tricks to "transport" (hopefully well documented) behavior from the used "child" module to the to the "parent" caller.

For instance taking your examples

• constants are implemented as functions with an empty prototype, hence can be exported like all normal functions.
• warnings and strict can be propagated like explained here ²

*) though it's possible, by exporting import , but doing so means mangling with the dark side, young padawan.

²) this should (?) work with all modules depending on Exporter

---

---

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.