3 ms·
Though to be fair, for the last year or so, every time I've needed to hack on a p5 script for $work, my first step has been to convert it to p6. It usually is
by colomon 11y ago
Though to be fair, for the last year or so, every time I've needed to hack on a p5 script for $work, my first step has been to convert it to p6. It usually is pretty quick for 50-100 line scripts, and generally it's a lot easier to reason about changing the code once it's in p6.
- raiph 11y agoWith apologies for the blizzard of questions: Do you have/write test suites? In P5? P6? Have you seriously tried any of the p5-to-p6 translators with your scripts? Was the usage message typically much-improved, about-the-same, or needs-work after your first successful compile? Same question for command line argument binding? Any speed stories? Scripts that started unacceptably slow but eventually got there? Ones that beat their Perl 5 originals? Ones that didn't really make it yet? Have you converted any of your Perl 6 conversions back in to Perl 5 code (to retain the clarity developed in the conversion to 6 but regain the speed that Perl 5 has)? Do any of your conversions use Perl 5 modules?