| Subject: | Moose and the debugger |
<mugwump> Alias: what's the problem with Moose and perl -d ?
<Alias> Seems harder to use...
<Alias> breakpoints seem trickier
<Alias> And stepping through things takes you to some unusal places
<jdv79> maybe that's what autarch means by wacktastic
<Alias> For example, I'm experimenting with Moose in Xtract.pm
<Alias> I have a method that fetching a list of database table names
<Alias> And then in each driver-specific subclass, it overloads the
method to do some refining (ignoring
sqlite internal tables for example)
<Khisanth> I think someone mentioned getting taken to anonymous code
refs other unnamed things :)
<Alias> But how do I set a breakpoint on that overload
<Alias> Or anywhere in that file, since there's no actual non-moosey
methods in it
<Alias> :/
<confound> Alias: file a bug
<Alias> Trouble is, and say what :)
<confound> pretty much what you just said
<confound> Moose is hard to use under perl -d because of X Y Z
<confound> no reason not to capture this kind of stuff
* confound/#moose never uses perl -d
<Alias> Or just cut and paste this conversation
<confound> yes, or that