However, I think the raptor meme belongs to the perl5+CPAN platform rather than to perl5 the language itself, so I chose not to try and force it onto the language.
]]>Of course, I'm joking.
I can't help the feeling that if the effort from all these years of Perl 5/Perl 6 attrition, had been directed into Perl 6 as they naturally should have been, it would have been ready some time ago. Instead the dog chooses to keep chewing on it's own leg.
]]>What I'm looking at here is a way to evolve a set of defaults without needing to understand any of the cleverer approaches - in my case, I think I'd rather have it imply 'use MyApp::Defaults;' or similar and centralize everything there with Syntaxt::Collector or sanity.pm or whatever - but I figured first I'd do the simplest thing that could possibly work and experiment.
I've got a pull request outstanding already that handles ~/.myperl and provides an environment variable; if you want to play around with changing the rewriter to generating a Syntax::Collector/sanity module and prepending a single line to invoke that to the .pm and script files, I'd be interested.
-- mst
]]>Getting from 'one line' to 'no lines' requires a trade-off - in this case 'run this using the myperl script, or apply myperl-rewrite to it'. Doc patches making this clearer would be welcome, but you can't have 'no lines' and 'your old code still works', and I somehow doubt nagios would be amazingly impressed if we broke half the existing plugins to make it easier to write new ones :)
]]>Do you plan to use Devel::Declare in the final version of p5-mop? Part of me thinks that there should be a better way or at least a formalized API to hack into the compiler.
]]>