NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Step One (Score:1)

by chromatic (983)

A custom runloop plus a little optional B::Op magic would fix up step one nice. If you can't do it in ten lines of code, that's because making B::Op's blessing code reusable is a lot more work than it should be.
My Hero (Score:2)

by malte (1708)

You'd be my hero!

I remember programming in VisualWorks for Smalltalk in the 90's where we'd start coding by putting a halt in the source code and then just debug the program until it was done.
A starting point... (Score:2)

by jesse (2531)

might be Devel::ebug.
Merge code (Score:1)

by scrottie (4167)

``"Merge newly compiled block into running program. (trivial? for non-closures. needs rebinding for closures)"''

Code::Splice. Cross your fingers, though.

Should work for closures. There's a fun bit of code in there that looks up the pad entries for variables in the source and target pads and changes the t_args to whatever the variable is named in the target. With the right t_arg and Perl providing the right pad for the closure, it should just kinda go.

Something that's been nagging me is how utterly cool d