When I am using tools is when I most want to fix them. But that is when I least can. Right now, for instance, I am trying to write some fricking PERL APPLICATIONS, but what do I have on my mind? The ways the tools should be better. I've even patched some of them:
- namespace::autoclean needs -except (patched on github)
- namespace::autoclean should support Mouse (patched on github)
- namespace::autoclean wipes out overload functions (patched on github)
- B::Hooks::EndOfScope calls the same callback more than once. sometimes (worked around on github, but I have no idea why that happens, and really we need real core feature for stuff like this, which are fairly obvious in implementation)
- Mouse introspection - method detection is lame (should work like autoclean)
- Moose inner/augment doesn't work if more than one function in a class uses it (lame)
- Method::Signatures::Simple has no invocant-less variant (obvious fix)
- Method::Signatures invocant-less variant causes assertion failures on Perl 5.12.1 when there is any syntax error elsewhere (wtf)
- NYTProf with Coro (crash and/or nonsense results)
- perl -d with Coro (crashola, so back to printf debugging)
- how cool a modern Perl debugger could be
Oh, and let's not even talk about the incredible panoply of core features and redesigns just asking to be written! First, for example, a real working is_num and is_str that I know how to do, just haven't been able to get to.
But I have actual programs to write, don't I?
Lesson learned: it's too late for Perl, but if I want to keep writing C++ productively, I conclude that I must never peek inside another C++ compiler for the rest of my life. And probably not the Boost libraries, either.
Comments