I suspect you're right, mostly. The issue that will eventually need to be addressed is this: Older nodes will all be talking about Perl 5, unless explicitly labled Perl 6. And newer nodes (flashing forward into the Perl 6 future) will be talking about Perl 6, without explicitly mentioning that fact. The result will be that as people search for some search term, they'll be getting Perl 5 answers that are not marked as such, Perl 5 answers that are marked as such, Perl 6 answers that are marked as Perl 6, and Perl 6 answers that are not marked as such, each from a progressively more recent timeframe in the history of the Perl community's collective mindset.

We already track and show the dates of nodes. Perl 5 solutions will still be useful in Perl 6. I just don't see a problem here beyond the usual problems that already exist.

- tye        

Perl 5 solutions will still be useful in Perl 6.

Maybe not. Module and algorithm advice will remain valid, but many people come looking for code snippets. Very basic things like the syntax will change in Perl 6. The elder monks will have no problem reading old and new code and telling them apart, but beginners will be confused if some nodes write  $a[3] and others  @a[3]. So it has to be made clear what version the node is talking about.

Of course, since Perl 6 is not exactly imminent, neither is this problem. (Things may be different with Parrot which is maturing faster).