2012.07.31 in #54On writing a new Perl Debugger (Part 1 - Why?)
Rocky Bernstein has started a new debugger for Perl. This the first part of an already 3-part long series of articles describing not only why he is building a new debugger, but also what can we expect to find in it. I think writing about the debugger as he is developing it can be one of the critical pieces, that can make the new debugger more popular than the previous ones.
2012.08.08 in #55To gdb or not to gdb
Another post from the series of Rocky Bernstein covering the writing of the new debugger. In this article he is discussing the question how much he should follow the established standard of gdb, and how much he can go on new, maybe better directions? He also helps us a bit to look around and see what happens in two different implementations of Ruby: MRI and Rubinius.
2012.09.13 in #60A plan for revamping and replacing the Perl debugger.
While Shlomi Fish is adding tests to the existing debugger, Rocky Bernstein is working on a replacement and Eric Johnson (kablamo) is working on Vim::Debug. Interesting times. I hope something improved will come out of this that can be easily hooked into GUIs and IDEs and won't be restricted to the command-line enabled people.
2015.06.30 in #206A Basic Challenge
A Challenge for you, though I am not sure if this is about implementing BASIC in Perl, compiling BASIC to Perl, or Compiling C++ to Perl.
2015.11.07 in #224Exact Perl location with B::Deparse (and Devel::Callsite)
To help figure out exactly where a program is stopped. E.g. in an expression like this: '$z = $x/$y + $c/$d;' to figure out which division threw the exception of 'illegal division by zero.'
2018.06.01 in #358Introducing B::DeparseTree
@rockyb is giving talk on the subject at the upcoming YAPC 2018 in Glasgow.
If you are not yet subscribed, you can do it now. Free of charge:
Just ONE e-mail each Monday. Easy to unsubscribe. No spam. Your e-mail address is safe.
This newsletter is about the Perl Programming languages.