in reply to Re^2: homespun GUI Wrapper for the Perl Debugger with an auto-refreshing editor (BBEdit on Mac OS X)
in thread Update: homespun GUI Wrapper for the Perl Debugger with an auto-refreshing editor (BBEdit on Mac OS X) (was: Perl Debugger: Is there a variable with the current source line number being traced?)

tl;dr .... :-|

Unfortunately I don't have the time to go into details ATM, but I think many modifications to perl5db.pl where unnecessary.

For instance you could have used persistent aliases instead of manipulating commands. The debugger has also an IDE interface to direct outputs to pipes.

If you can't get ptkdb running on your Mac because of TK version problems (which is really weird and merits a thread of its own) try giving emacs a try, which has more or less the reference implementation of debugger integration.

With Aquamacs you'll even get standard Mac behaviour.

Try M-x perldb.

For more tricks of how to patch the debugger please see the slides I linked in the thread I linked to before.

HTH :)

Cheers Rolf

( addicted to the Perl Programming Language)

  • Comment on Re^3: homespun GUI Wrapper for the Perl Debugger with an auto-refreshing editor (BBEdit on Mac OS X)

Replies are listed 'Best First'.
Re^4: homespun GUI Wrapper for the Perl Debugger with an auto-refreshing editor (BBEdit on Mac OS X)
by Shoveler (Acolyte) on Feb 26, 2014 at 17:25 UTC
    I haven't even done "many" changes to perl5db.pl to begin with! ;-)

    It's been less than 20 lines in total (including the AppleScript ones shown above), and in only 3 places.

    And how would aliases help me? Aliases can't seem to add actual functionality – they only alias existing functionality for shorthand invocation as far as I can tell. But I actually need additional functionality.

    Do you happen to know where to look for the IDE interface? I hadn't noticed it so far. But in that case I would have had to create a separate intermediate process; Sounds like a lot of additional complexity...

    Of course I agree that that might be cleaner, if it can actually achieve what I need.

    Emacs wouldn't be an advantage for me – it would introduce a whole additional editor environment with different usage, different presentation and a substantial learning curve. The BBEdit solution actually works surprisingly well already.

    Interesting information and hints from you and above, in any case. While I might eventually end up changing things from where I'm now, I'm quite stoked about the level of usability I've managed to wring out of this provisional solution already with a minimum of customization.

    Many thanks to everybody anyway! :-)