For this reason, a set of Synopses was published, each one relating the contents of an Apocalypse, but with any subsequent changes reflected in updates.

Today, the Raku specification is managed through the "roast" testing suite,[14] while the Synopses are kept as a historical reference.

[15] There is also a series of Exegeses written by Damian Conway that explain the content of each Apocalypse in terms of practical usage.

These included the confusion surrounding sigil usage for containers, the ambiguity between the select functions, and the syntactic impact of bareword filehandles.

There were many other problems that Perl programmers had discussed fixing for years, and these were explicitly addressed by Wall in his speech.

Since backward compatibility is a common goal when enhancing software, the breaking changes in Perl 6 had to be stated explicitly.

Spiral designs embedded in her butterfly-like wings resemble the characters "P6", the favored nickname for Perl 6, and off-center eye placement is an intentional pun on "Wall-eyed".

[19] One of the goals behind the lively and colorful design of the logo was to discourage misogyny in the community and for it to be an opportunity for those of "masculine persuasion" to show their sensitive side.

Pugs used to be the most advanced implementation of Perl 6, but since mid 2007, it is mostly dormant (with updates made only to track the current version of the Glasgow Haskell Compiler (GHC)).

In theory, anything capable of parsing the STD and generating executable code is a suitable bootstrapping system for Perl 6. kp6 is currently compiled by mp6 and can work with multiple backends.

As a result, it required an existing Perl 6 interpreter, such as one of the Rakudo Star releases, to run.