Re^5: Dumping variables but DRY and simple

[rovf]

Anyway I'm not sure if there are sideeffects when trying to access the file...

This would *really* be a hack. For instance, the file might already have been changed after the program has been started (a quite common situation during development). But yes, it is a clever idea.

[LanX]

There are more options:

Furthermore, when called from within the DB package, caller returns more detailed information: it sets the list variable @DB::args to be the arguments with which the subroutine was invoked.

Whatever this practically means... anyway I need the dumping for debugging and as rubasov said any keystroke saved is a bless while debugging.

OR

I could pass only the variable _names_ and use PadWalker and Stash to get the references/values in caller's context.

But as stated in the OP I don't wanna reinvent the wheel...