Re^7: Monkey patching all subs with a basic 'starting subname' message (trace perldebugger)

> sub HOW_DO_I_GET_$original_proto_IN_HERE? {

AFAIK it's only possible via eval, if you think you've already delegated the maximum possible into closures, you should be fine.

I'm sure if you dig long enough into CPAN you'll find some (semi-) official hack to change the prototype.

YMMV.

Good luck

PS: Hope you're already aware of the trace options in perldebug

frame

Affects the printing of messages upon entry and exit from subroutines.
+ If frame & 2 is false, messages are printed on entry only. (Printing
+ on exit might be useful if interspersed with other messages.)

If frame & 4 , arguments to functions are printed, plus context and ca
+ller info. If frame & 8 , overloaded stringify and tied FETCH is enab
+led on the printed arguments. If frame & 16 , the return value from t
+he subroutine is printed.

The length at which the argument list is truncated is governed by the 
+next option:
[download]

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

Comment on Re^7: Monkey patching all subs with a basic 'starting subname' message (trace perldebugger) Select or Download Code

Replies are listed 'Best First'.
Re^8: Monkey patching all subs with a basic 'starting subname' message by Anonymous Monk on Jul 19, 2017 at 13:04 UTC
> Hope you're already aware of the trace options in perldebug I am now; and that, of course, is what I needed at the time! I am enlightened! Thanks.	[reply]


Perl Monk, Perl Meditation
	PerlMonks