I'm not sure that's going to be necessary. The transition from Perl4 to Perl5 seems to have happened pretty seamlessly, with newer idioms slowly replacing older ones. I think it'll be interesting (entertaining, fun, perhaps even a little frustrating) to watch the Community adapt to Perl6 when it's released.

It may be wise to begin training ourselves to mention the Perl version, but I think that's really all the differentiation we'll need. I really don't think we'll need a separate site. (At least I hope not.)

Indeed, there may be some benefit to keeping the new lessons on the same site, as that will help communicate the availability of the new version, as well as people's experiences with it.

--f

Update: Ack. Typo. Fixed. (Feel free to tell me. Puhleeeessssse, Eddie.)

Can I bring up the subject again of

  <CODE v6>
[download]

to tag individual blocks? It could automatically show up on the node somehow.

Would adding:

require 6.0; # or whatever it turns out to be

to any relevant samples work instead? That way, we save TFL some work.

--f

Have fun,
Carl Forde

# perl 5ish
use strict;
use warnings;
use diagnostics;
use CGI;

#perl6ish
pragma strict;     #
pragma warnings;   # No guarantees on what he picks for command names!
pragma diagnostics;#
method CGI;        # They might all be "method" or "invoke" or "%#$" =
+)
[download]

At worst, vroom adds a checkbox for "perl6?" and defaults it off for all old posts...

--
$you = new YOU;
honk() if $you->love(perl)

—John