Indeed. But the book is about Perl5. Perl6 is such a different language that someone moving from Perl5->Perl6 will likely be mostly/completely a rewrite.
... unless, I suppose, they are following the practices in Modern Perl ala Moose and some other things. I guess maaayybbeee they could translate across. But it would be touching ever single line, in a transformation that would be on par with switching to Ruby (or Python I suppose).
It seems disingenuous to imply that moving to Perl 6 from Perl 5 is akin to switching to Ruby or Python (much less "touching every single line"). Perl 6 supports Perl 5 syntax with Inline::Perl5. So, in theory, one could move Perl 5 code directly into a Perl 6 project without changing much at all.
Edited: an earlier version of this comment that referred to an outdated FAQ (mentioning a perl 5 to 6 translator).
Yes, I updated my comment, but my point still stands: Perl 6 supports Perl 5 syntax and migrating is nowhere near as hard as was implied. Sorry for confusion.
Your comment is still blatant disinformation. By the same measure Perl6 is also Python and Java and JavaScript, because somebody could make an Inline:: for any of those.
You could say that a number of hooks exist to make it easier to write various Inline:: variants, and you would be correct. But claiming that there is a special soft spot for the Perl5 interpreter is factually wrong.
What disinformation? Perl 5 is supported when using Perl 6. The comment I replied to states:
"Perl6 is such a different language that someone moving from Perl5->Perl6 will likely be mostly/completely a rewrite."
Rewriting is not always necessary due to Perl5 support.
The comment further states:
"I guess maaayybbeee they could translate across. But it would be touching ever single line, in a transformation that would be on par with switching to Ruby (or Python I suppose)."
Touching every single line is technically not necessary due to Perl 5 support.
To your comment:
"But claiming that there is a special soft spot for the Perl5 interpreter is factually wrong."
Nowhere in my comments did I make any such claim. I was simply refuting the statement that people with Perl 5 code will have such a difficult time with Perl 6 that it would be just as painful as dropping all their Perl code and switching languages.
Although to switch to ruby or python you'd likely end up either typing out a lot of things Moo(se) give you or trying to port them (see also the MooseX gem and Elk)
... unless, I suppose, they are following the practices in Modern Perl ala Moose and some other things. I guess maaayybbeee they could translate across. But it would be touching ever single line, in a transformation that would be on par with switching to Ruby (or Python I suppose).