[lemma=if]? □
[lemma=if]? □ □
[lemma=if]? □?
After all , that 's just what we did for ordinary quotes in the transition from Perl 4 to Perl 5 . The second will be a Perl 6 version of the existing PODs - or at least all the ones that make sense . Dave Mitchell proposed " PDD : Conventions and Guidelines for Perl Source Code " to try to establish some coding standards for Perl 6 . It was a much different perspective from the ones pitched before , as it was based on what he sees as the problems in Perl 5 , untainted by the Perl 6 process ( which he has not been following ) . In Perl 4 it undefines the associated scalar ( but may have other side effects including SEGVs ) . substr ( ) , join ( ) , repeat ( ) , reverse ( ) , quotemeta ( ) and string concatenation were all handling Unicode strings incorrectly in Perl 5.6.0 . If Perl 5 arrays ( even with only a pseudo-multi-dimensional nature to them ) are n't fundamentally in sync with database access , then to make them so would require rendering them out sync with everything else they've been used for. Dan also asked for opnions on who should decode opcode function arguments - the functions or the dispatch loop ? In Perl 4 the return value of push was undocumented , but it was actually the last value being pushed onto the target list . Perl 4 library scripts should continue to work with no problems . A perfect example is Larry 's " module " solution to the Perl 6 vs. Perl 5 interpretation ( although it still needs a few extra lights here and there to make it really work ) .