I should point out that none of the points were listed because they were bad programming practice. (I'm worrying about cache line spills and writing assembly code--bad perl programming practice is just not a concern :) I listed them because they all take advantage of what could be considered "interesting aspects" of the perl interpreter engine, aspects that we're not preserving in their entirety (or at all) in Parrot.

Having said that, it's really likely that things like:

*foo = \$bar;
[download]

will work just fine when translated to perl 6, I'm just not sure I want to guarantee that

*foo = *bar;
[download]

will get everything the way we might like, at least if you're doing some of the odder things.