{"id":22672,"date":"2023-02-28T03:08:01","date_gmt":"2023-02-28T03:08:01","guid":{"rendered":"https:\/\/www.booksofall.com\/es\/?post_type=product&p=22672"},"modified":"2023-02-28T03:08:01","modified_gmt":"2023-02-28T03:08:01","slug":"raku-one-liners","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/es\/raku-one-liners\/","title":{"rendered":"Raku One-Liners"},"content":{"rendered":"

Raku\u00a0is a member of the\u00a0Perl<\/a>\u00a0family of\u00a0programming languages<\/a>. Formerly known as\u00a0Perl 6, it was renamed in October 2019.\u00a0Raku<\/a>\u00a0introduces elements of many modern and historical languages. Compatibility with Perl was not a goal, though a\u00a0compatibility mode<\/a>\u00a0is part of the specification. The design process for Raku began in 2000.<\/p>\n

The Raku design process was first announced on 19 July 2000, on the fourth day of that year\u2019s Perl Conference, by Larry Wall in his State of the Onion 2000 talk. At that time, the primary goals were to remove \u201chistorical warts\u201d from the language; \u201ceasy things should stay easy, hard things should get easier, and impossible things should get hard\u201d; a general cleanup of the internal design and APIs. The process began with a series of requests for comments or \u201cRFCs\u201d. This process was open to all contributors and left no aspect of the language closed to change.<\/p>\n

Once the RFC process was complete, Wall reviewed and classified each of the 361 requests received. He then began the process of writing several \u201cApocalypses\u201d, using the original meaning of the term, \u201crevealing\u201d. While the original goal was to write one Apocalypse for each chapter of\u00a0Programming Perl<\/a>, it became obvious that, as each Apocalypse was written, previous Apocalypses were being invalidated by later changes. 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 \u201croast\u201d testing suite, while the Synopses are kept as a historical reference.<\/p>\n

There are also a series of Exegeses written by Damian Conway that explain the content of each Apocalypse in terms of practical usage. Each Exegesis consists of code examples along with a discussion of the usage and implications of the examples.<\/p>\n

There are three primary methods of communication used in the development of Raku today. The first is the raku IRC channel on Libera Chat. The second is a set of mailing lists. The third is the Git source code repository hosted at GitHub.<\/p>\n","protected":false},"excerpt":{"rendered":"