Please note that the content of this book primarily consists of articles available from Wikipedia or other free sources online. Pages: 89. Chapters: Aliasing (computing), Array slicing, Binary logarithm, Boilerplate (text), Chain-of-responsibility pattern, Comment (computer programming), Dispatch table, Do while loop, Extensibility pattern, Foreach loop, Fork (operating system), For loop, Function object, Generator (computer programming), Hello world program examples, Immutable object, Iterator pattern, Leaning toothpick syndrome, Mutator method, One-liner program, Parallel array, Perl 6, Perl language structure, Polymorphism in object-oriented programming, Schwartzian transform, SEDOL, Short-circuit evaluation. Excerpt: Perl 6 is a member of the Perl family of programming languages. It is still in development as a specification from which several interpreter and compiler implementations are being written. It is introducing elements of many modern and historical languages. Perl 6 is intended to have many implementations. Compatibility with Perl 5 is not a goal, though a compatibility mode is part of the specification. The design process for Perl 6 began in 2000. Development on Pugs, the first high-traction implementation, began in 2005, and today there are multiple Perl 6 implementation projects. Rakudo Perl is based on Parrot and NQP (Not Quite Perl), and releases a new version every month; in July 2010, the project released the first Rakudo Star distribution, a useful and usable collection of a Perl 6 implementation and related materials. Larry Wall maintains a reference grammar known as STD.pm6, written in Perl 6 and bootstrapped with Perl 5. Niecza, another major Perl 6 implementation, focuses on optimization and efficient implementation research. It targets the Common Language Infrastructure. In Perl 6, we decided it would be better to fix the language than fix the user - Larry Wall The Perl 6 design process was first announced on July 19, 2000, on the fourth day of that year's Perl Conference, by Larry Wall in his State of the Onion 2000 talk. At that time, the primary goals were to remove "historical warts" from the language; "easy things should stay easy, hard things should get easier, and impossible things should get hard;" a general cleanup of the internal design and APIs. The process began with a series of requests for comments or "RFCs." This process was open to all contributors, and left no aspect of the language closed to change. Once the RFC process was complete, Wall reviewed and classified each request (361 were received). He then began the process of writing several "Apocalypses," a term which means "revealing." While the original goal was to write one Apocalypse f