NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
PPI? (Score:1)
I'm not all that excited to see this requiring PPI. It's really just a much better-tested hack rather than a solution, and IIRC (cpandeps is down) it pulls in half the world in dependencies. What happens if you want to get Method::Signatures, or something like it, into core? Default values are nice, but are they worth the complexity?
Re: (Score:2)
When it goes into core it doesn't go in as a module, it goes in as syntax. No fucking around with PPI, the Perl parser gets patched.
And trust me, PPI is the least terrifying dependency Method::Signatures uses. Its deps are shallow and mundane. It's battle tested (Perl::Critic has been knocking it around for a long time), easy to figure out what the hell its doing and it does what it says on the tin.
Really, you should have seen what I was trying to do with Text::Balanced. That was a swamp and it didn't e
Re:PPI? (Score:1)
I agree. PPI is solid.
Reply to This
Parent