Re^4: Splitting program into modules

> Again, it's intrusive;

I wonder why you prefer it that way, there are at least two alternatives

running under the debugger and activating the trace option
inspecting the stash of the included packages and dynamically monkey patching the subs with tracing wrappers.

Am I missing something?

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

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

Comment on Re^4: Splitting program into modules

Replies are listed 'Best First'.
Re^5: Splitting program into modules by stevieb (Canon) on Nov 14, 2018 at 14:21 UTC
I definitely don't prefer it this way. This was a project I started many, many years ago actually. It was one of the very first projects I ever thought of when I started writing Perl, and it took many years to put together. It was more a "can I do this" thing :) As a matter of fact, another project I went on for the sake of learning how is monkey patching on the fly with my Mock::Sub and Wrap::Sub, so updating Devel::Trace::Subs is something I definitely could do to remove the actual writing to files. I'll create myself an issue so I don't forget to do this someday.	[reply]

Replies are listed 'Best First'.

Re^5: Splitting program into modules
by stevieb (Canon) on Nov 14, 2018 at 14:21 UTC

I definitely don't prefer it this way. This was a project I started many, many years ago actually. It was one of the very first projects I ever thought of when I started writing Perl, and it took many years to put together. It was more a "can I do this" thing :)

As a matter of fact, another project I went on for the sake of learning how is monkey patching on the fly with my Mock::Sub and Wrap::Sub, so updating Devel::Trace::Subs is something I definitely could do to remove the actual writing to files. I'll create myself an issue so I don't forget to do this someday.

[reply]