Front page | perl.perl5.porters |
Postings from November 2011
* Konovalov, Vadim <vadim.konovalov@alcatel-lucent.com> [2011-11-25 19:05]: > this logic does not work here, because perl5db.pl is not "any code". Why? > Due to specifics of perl debugger interface. There are modules on CPAN that interface with the perl debugger outside of using perl5db.pl that are not written in such an ugly way. So if this is your only justification for the above claim, then the claim is false. > I see a very special beauty of having all implemented in a single file > having some 322,595 bytes in size. That’s… touching. > Adding modularity there will bring us forest of unneeded files and > then introduce bugs. … Why? > Once again: perl5db is some highly efficient implemented internals > that is not "any code" starving for "use strict" Just because you believe that does not mean it’s true. Do you have actual basis to claim the code is highly efficient? Or are you just saying that because, well, surely there must be a reason when code is very ugly, right? Have you seen Devel::ebug? Did you understand that this was originally supposed to be written on top of perl5db.pl which turned out not to be feasible? I also remember recently spelunking in perl5db.pl’s internals to hack in some very simple features that should really have a) UI affordance and b) programmatic API. There are so many features and use cases in debugging people have asked for, which perl5db.pl does not cover and, because it is this monolithic pile of mud, never will: no one is willing to be covered in mud to add them. Now maybe you like your early ’90s technology just the way it has always been, but that is no reason to stand in the way of people who want more out of it. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>Thread Previous | Thread Next