DepositaryO Wiki

Padron:About Padron:Good article Padron:Infobox programming language

Perl is a high-level, general-purpose, interpreted, dynamic programming language. Though Perl is not officially an acronym,[1] there are various backronyms in usage, such as: Practical Extraction and Reporting Language.[2] Perl was originally developed by Larry Wall in 1987 as a general-purpose Unix scripting language to make report processing easier.[3] Since then, it has undergone many changes and revisions and become widely popular amongst programmers. Larry Wall continues to oversee development of the core language, and its upcoming version, Perl 6. Perl borrows features from other programming languages including C, shell scripting (sh), AWK, and sed.[4] The language provides powerful text processing facilities without the arbitrary data length limits of many contemporary Unix tools,[5] facilitating easy manipulation of text files. Perl gained widespread popularity in the late 1990s as a CGI scripting language, in part due to its parsing abilities.[6]

In addition to CGI, Perl is used for graphics programming, system administration, network programming, finance, bioinformatics, and other applications. Perl is nicknamed "the Swiss Army chainsaw of programming languages" because of its flexibility and power.[7] In 1998, it was also referred to as the "duct tape that holds the Internet together", in reference to its ubiquity and perceived inelegance.[8]


Early versions[]

Larry Wall began work on Perl in 1987, while working as a programmer at Unisys,[5] and released version 1.0 to the comp.sources.misc newsgroup on December 18, 1987.[9] The language expanded rapidly over the next few years.

Perl 2, released in 1988, featured a better regular expression engine. Perl 3, released in 1989, added support for binary data streams.

Originally the only documentation for Perl was a single (increasingly lengthy) man page. In 1991, Programming Perl, known to many Perl programmers as the "Camel Book" because of its cover, was published and became the de facto reference for the language. At the same time, the Perl version number was bumped to 4, not to mark a major change in the language but to identify the version that was documented by the book.

Early Perl 5[]

Perl 4 went through a series of maintenance releases, culminating in Perl 4.036 in 1993. At that point, Wall abandoned Perl 4 to begin work on Perl 5. Initial design of Perl 5 continued into 1994. The perl5-porters mailing list was established in May 1994 to coordinate work on porting Perl 5 to different platforms. It remains the primary forum for development, maintenance, and porting of Perl 5.[10]

Perl 5.000 was released on October 17, 1994.[11] It was a nearly complete rewrite of the interpreter, and it added many new features to the language, including objects, references, lexical (my) variables, and modules. Importantly, modules provided a mechanism for extending the language without modifying the interpreter. This allowed the core interpreter to stabilize, even as it enabled ordinary Perl programmers to add new language features. Perl 5 has been in active development since then.

Perl 5.001 was released on March 13, 1995. Perl 5.002 was released on February 29, 1996 with the new prototypes feature. This allowed module authors to make subroutines that behaved like Perl builtins. Perl 5.003 was released June 25, 1996, as a security release.

One of the most important events in Perl 5 history took place outside of the language proper and was a consequence of its module support. On October 26, 1995, the Comprehensive Perl Archive Network (CPAN) was established as a repository for Perl modules and Perl itself; as of April 2012, it carries over 24,500 modules by more than 9,500 authors.[12]

Perl 5.004 was released on May 15, 1997, and included among other things the UNIVERSAL package, giving Perl a base object to which all classes were automatically derived and the ability to require versions of modules. Another significant development was the inclusion of the module,[13] which contributed to Perl's popularity as a CGI scripting language.[14]

Perl also now supported running under Microsoft Windows and several other operating systems.[13]

Perl 5.005 was released on July 22, 1998. This release included several enhancements to the regex engine, new hooks into the backend through the B::* modules, the qr// regex quote operator, a large selection of other new core modules, and added support for several more operating systems, including BeOS.[15]


Perl 5.6 was released on March 22, 2000. Major changes included 64-bit support, Unicode string representation, large file support (i.e. files over 2 GiB) and the "our" keyword.[16][17] When developing Perl 5.6, the decision was made to switch the versioning scheme to one more similar to other open source projects; after 5.005_63, the next version became 5.5.640, with plans for development versions to have odd numbers and stable versions to have even numbers.

In 2000, Larry Wall put forth a call for suggestions for a new version of Perl from the community. The process resulted in 361 RFC (request for comments) documents which were to be used in guiding development of Perl 6. In 2001,[18] work began on the apocalypses for Perl 6, a series of documents meant to summarize the change requests and present the design of the next generation of Perl. They were presented as a digest of the RFCs, rather than a formal document. At this point, Perl 6 existed only as a description of a language.

Perl 5.8 was first released on July 18, 2002, and had nearly yearly updates since then. The latest version of Perl 5.8 is 5.8.9, released December 14, 2008. Perl 5.8 improved unicode support, added a new IO implementation, added a new thread implementation, improved numeric accuracy, and added several new modules.[19]

In 2004, work began on the Synopses – originally documents that summarized the Apocalypses, but which became the specification for the Perl 6 language. In February 2005, Audrey Tang began work on Pugs, a Perl 6 interpreter written in Haskell.[20] This was the first concerted effort towards making Perl 6 a reality. This effort stalled in 2006.[21]

On December 18, 2007, the 20th anniversary of Perl 1.0, Perl 5.10.0 was released. Perl 5.10.0 included notable new features, which brought it closer to Perl 6. These included a switch statement (called "given"/"when"), regular expressions updates, and the smart match operator, "~~".[22][23] Around this same time, development began in earnest on another implementation of Perl 6 known as Rakudo Perl, developed in tandem with the Parrot virtual machine. As of November 2009, Rakudo Perl has had regular monthly releases and now is the most complete implementation of Perl 6.

A major change in the development process of Perl 5 occurred with Perl 5.11; the development community has switched to a monthly release cycle, with planned release dates three months ahead.

On April 12, 2010, Perl 5.12.0 was released. Notable core enhancements include new package NAME VERSION syntax, the Yada Yada operator (intended to mark placeholder code that is not yet implemented), implicit strictures, full Y2038 compliance, regex conversion overloading, DTrace support, and Unicode 5.2.[24] On January 21, 2011, Perl 5.12.3 was released; it contains updated modules and some documentation changes.[25] Version 5.12.4 was released on June 20, 2011.

On May 14, 2011, Perl 5.14 was released. On September 26, 2011, the latest version, 5.14.2, was released.

The latest development release of Perl 5 is 5.15.8, released by Max Maischein on February 20, 2012.


Perl was originally named "Pearl". Larry Wall wanted to give the language a short name with positive connotations; he claims that he considered (and rejected) every three- and four-letter word in the dictionary. He also considered naming it after his wife Gloria. Wall discovered the existing PEARL programming language before Perl's official release and changed the spelling of the name.[26]

When referring to the language, the name is normally capitalized (Perl) as a proper noun. When referring to the interpreter program itself, the name is often uncapitalized (perl) because most Unix-like file systems are case-sensitive. Before the release of the first edition of Programming Perl, it was common to refer to the language as perl; Randal L. Schwartz, however, capitalized the language's name in the book to make it stand out better when typeset. This case distinction was subsequently documented as canonical.[27]

There is some contention about the all-caps spelling "PERL", which the documentation declares incorrect[27] and which some core community members consider a sign of outsiders.[28] The name is occasionally backronymed as Practical Extraction and Report Language, which appears at the top of the documentation[26] and in some printed literature.[29] Several backronyms have been suggested as equally canonical, including Wall's own humorous Pathologically Eclectic Rubbish Lister.[30] Indeed, Wall claims that the name was intended to inspire many different expansions.[31]

Camel symbol[]

Programming Perl, published by O'Reilly Media, features a picture of a camel on the cover and is commonly referred to as the "Camel Book".[32] This image of a camel has become an unofficial symbol of Perl as well as a general hacker emblem, appearing on T-shirts and other clothing items.

O'Reilly owns the image as a trademark but licenses it for non-commercial use, requiring only an acknowledgement and a link to Licensing for commercial use is decided on a case by case basis.[33] O'Reilly also provides "Programming Republic of Perl" logos for non-commercial sites and "Powered by Perl" buttons for any site that uses Perl.[33]

Onion symbol[]

The Perl Foundation owns an alternative symbol, an onion, which it licenses to its subsidiaries, Perl Mongers, PerlMonks,, and others.[34] The symbol is a visual pun on pearl onion.[35]


Padron:Main Perl is a general-purpose programming language originally developed for text manipulation, but Padron:As of is used for a wide range of tasks including system administration, web development, network programming, games, bioinformatics, and GUI development.

The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal).[36] Its major features include support for multiple programming paradigms (procedural, object-oriented, and functional styles), reference counting memory management (without a cycle-detecting garbage collector), built-in support for text processing, and a large collection of third-party modules.

According to Larry Wall, Perl has two slogans. The first is "There's more than one way to do it", commonly known as TMTOWTDI. The second slogan is "Easy things should be easy and hard things should be possible".[5]


The overall structure of Perl derives broadly from C. Perl is procedural in nature, with variables, expressions, assignment statements, brace-delimited blocks, control structures, and subroutines.

Perl also takes features from shell programming. All variables are marked with leading sigils, which unambiguously identify the data type (for example, scalar, array, hash) of the variable in context. Importantly, sigils allow variables to be interpolated directly into strings. Perl has many built-in functions that provide tools often used in shell programming (although many of these tools are implemented by programs external to the shell) such as sorting, and calling on system facilities.

Perl takes lists from Lisp, hashes ("associative arrays") from AWK, and regular expressions from sed. These simplify and facilitate many parsing, text-handling, and data-management tasks.

Perl 5 added features that support complex data structures, first-class functions (that is, closures as values), and an object-oriented programming model. These include references, packages, class-based method dispatch, and lexically scoped variables, along with compiler directives (for example, the strict pragma). A major additional feature introduced with Perl 5 was the ability to package code as reusable modules. Larry Wall later stated that "The whole intent of Perl 5's module system was to encourage the growth of Perl culture rather than the Perl core."[37]

All versions of Perl do automatic data-typing and automatic memory-management. The interpreter knows the type and storage requirements of every data object in the program; it allocates and frees storage for them as necessary using reference counting (so it cannot deallocate circular data structures without manual intervention). Legal type-conversions — for example, conversions from number to string — are done automatically at run time; illegal type conversions are fatal errors.


The design of Perl can be understood as a response to three broad trends in the computer industry: falling hardware costs, rising labor costs, and improvements in compiler technology. Many earlier computer languages, such as Fortran and C, aimed to make efficient use of expensive computer hardware. In contrast, Perl is designed to make efficient use of expensive computer-programmers.

Perl has many features that ease the task of the programmer at the expense of greater CPU and memory requirements. These include automatic memory management; dynamic typing; strings, lists, and hashes; regular expressions; introspection; and an eval() function. Perl follows the theory of "no built-in limits",[32] an idea similar to the Zero One Infinity rule.

Wall was trained as a linguist, and the design of Perl is very much informed by linguistic principles. Examples include Huffman coding (common constructions should be short), good end-weighting (the important information should come first), and a large collection of language primitives. Perl favors language constructs that are concise and natural for humans to write, even where they complicate the Perl interpreter.

Perl syntax reflects the idea that "things that are different should look different."[38] For example, scalars, arrays, and hashes have different leading sigils. Array indices and hash keys use different kinds of braces. Strings and regular expressions have different standard delimiters. This approach can be contrasted with languages such as Lisp, where the same S-expression construct and basic syntax are used for many different purposes.

Perl does not enforce any particular programming paradigm (procedural, object-oriented, functional, or others) or even require the programmer to choose among them.

There is a broad practical bent to both the Perl language and the community and culture that surround it. The preface to Programming Perl begins: "Perl is a language for getting your job done."[5] One consequence of this is that Perl is not a tidy language. It includes many features, tolerates exceptions to its rules, and employs heuristics to resolve syntactical ambiguities. Because of the forgiving nature of the compiler, bugs can sometimes be hard to find. Perl's function documentation remarks on the variant behavior of built-in functions in list and scalar contexts that "In general, they do what you want, unless you want consistency."[39]

No written specification or standard for the Perl language exists for Perl versions through Perl 5, and there are no plans to create one for the current version of Perl. There has been only one implementation of the interpreter, and the language has evolved along with it. That interpreter, together with its functional tests, stands as a de facto specification of the language. Perl 6, however, started with a specification,[40] and several projects[41] aim to implement some or all of the specification.


Perl has many and varied applications, compounded by the availability of many standard and third-party modules.

Ever since the early days of the Web, programmers have used Perl to write CGI scripts. Perl is known as one of "the three Ps" (along with Python and PHP), the most popular dynamic languages for writing Web applications. It is also an integral component of the popular LAMP solution stack for web development. Large projects written in Perl include cPanel, Slash, Bugzilla, RT, TWiki, and Movable Type. Many high-traffic websites use Perl extensively. Examples include,,, Craigslist,[42] IMDb,[43] LiveJournal, Slashdot and Ticketmaster.

Perl is often used as a glue language, tying together systems and interfaces that were not specifically designed to interoperate, and for "data munging",[44] that is, converting or processing large amounts of data for tasks such as creating reports. In fact, these strengths are intimately linked. The combination makes Perl a popular all-purpose language for system administrators, particularly because short programs can be entered and run on a single command line.

With a degree of care, Perl code can be made portable across Windows and Unix. Portable Perl code is often used by suppliers of software (both COTS and bespoke) to simplify packaging and maintenance of software build- and deployment-scripts.

Graphical user interfaces (GUIs) may be developed using Perl. For example, Perl/Tk is commonly used to enable user interaction with Perl scripts. Such interaction may be synchronous or asynchronous, using callbacks to update the GUI. For more information about the technologies involved, see Tk, Tcl and WxPerl.

Perl is also widely used in finance and in bioinformatics, where it is valued for rapid application development and deployment and for its capability to handle large data-sets.


Perl is implemented as a core interpreter, written in C, together with a large collection of modules, written in Perl and C. Padron:As of, the stable version (5.12.3) is 14.2 MB when packaged in a tar file and gzip compressed.[45] The interpreter is 150,000 lines of C code and compiles to a 1 MB executable on typical machine architectures. Alternatively, the interpreter can be compiled to a link library and embedded in other programs. There are nearly 500 modules in the distribution, comprising 200,000 lines of Perl and an additional 350,000 lines of C code. (Much of the C code in the modules consists of character-encoding tables.)

The interpreter has an object-oriented architecture. All of the elements of the Perl language—scalars, arrays, hashes, coderefs, filehandles—are represented in the interpreter by C structs. Operations on these structs are defined by a large collection of macros, typedefs, and functions; these constitute the Perl C API. The Perl API can be bewildering to the uninitiated, but its entry points follow a consistent naming-scheme, which provides guidance to those who use it.

The life of a Perl interpreter divides broadly into a compile phase and a run phase.[46] In Perl, the phases are the major stages in the interpreter's life-cycle. Each interpreter goes through each phase only once, and the phases follow in a fixed sequence.

Most of what happens in Perl's compile phase is compilation, and most of what happens in Perl's run phase is execution, but there are significant exceptions. Perl makes important use of its capability to execute Perl code during the compile phase. Perl will also delay compilation into the run phase. The terms that indicate the kind of processing that is actually occurring at any moment are compile time and run time. Perl is in compile time at most points during the compile phase, but compile time may also be entered during the run phase. The compile time for code in a string argument passed to the eval built-in occurs during the run phase. Perl is often in run time during the compile phase and spends most of the run phase in run time. Code in BEGIN blocks executes at run time but in the compile phase.

At compile time, the interpreter parses Perl code into a syntax tree. At run time, it executes the program by walking the tree. Text is parsed only once, and the syntax tree is subject to optimization before it is executed, so that execution is relatively efficient. Compile-time optimizations on the syntax tree include constant folding and context propagation, but peephole optimization is also performed.

Perl has a Turing-complete grammar because parsing can be affected by run-time code executed during the compile phase.[47] Therefore, Perl cannot be parsed by a straight Lex/Yacc lexer/parser combination. Instead, the interpreter implements its own lexer, which coordinates with a modified GNU bison parser to resolve ambiguities in the language.

It is often said that "Only perl can parse Perl",[48] meaning that only the Perl interpreter (perl) can parse the Perl language (Perl), but even this is not, in general, true. Because the Perl interpreter can simulate a Turing machine during its compile phase, it would need to decide the Halting Problem in order to complete parsing in every case. It's a long-standing result that the Halting Problem is undecidable, and therefore not even perl can always parse Perl. Perl makes the unusual choice of giving the user access to its full programming power in its own compile phase. The cost in terms of theoretical purity is high, but practical inconvenience seems to be rare.

Other programs that undertake to parse Perl, such as source-code analyzers and auto-indenters, have to contend not only with ambiguous syntactic constructs but also with the undecidability of Perl parsing in the general case. Adam Kennedy's PPI project focused on parsing Perl code as a document (retaining its integrity as a document), instead of parsing Perl as executable code (which not even Perl itself can always do). It was Kennedy who first conjectured that "parsing Perl suffers from the 'Halting Problem'",[49] which was later proved.[50]

Perl is distributed with some 120,000 functional tests. These run as part of the normal build process and extensively exercise the interpreter and its core modules. Perl developers rely on the functional tests to ensure that changes to the interpreter do not introduce bugs; additionally, Perl users who see that the interpreter passes its functional tests on their system can have a high degree of confidence that it is working properly.

Maintenance of the Perl interpreter has become increasingly difficult over the years. The code base has undergone continuous development since 1994. The code has been optimized for performance at the expense of simplicity, clarity, and strong internal interfaces. New features have been added, yet virtually complete backward compatibility with earlier versions is maintained. Major releases of Perl were coordinated by Perl pumpkings,[51] which handled integrating patch submissions and bug fixes, but the language has since changed to a rotating, monthly release cycle. Development discussion takes place via the perl5_porters mailing list. As of Perl 5.11, development efforts have included refactoring certain core modules known as 'dual lifed' modules out of the Perl core[52] to help alleviate some of these problems.


Perl is dual licensed under both the Artistic License and the GNU General Public License. Distributions are available for most operating systems. It is particularly prevalent on Unix and Unix-like systems, but it has been ported to most modern (and many obsolete) platforms. With only six reported exceptions, Perl can be compiled from source code on all POSIX-compliant, or otherwise-Unix-compatible platforms.[53]

Because of unusual changes required for the Mac OS Classic environment, a special port called MacPerl was shipped independently.[54]

The Comprehensive Perl Archive Network carries a complete list of supported platforms with links to the distributions available on each.[55] CPAN is also the source for publicly available Perl modules that are not part of the core Perl distribution.


Users of Microsoft Windows typically install one of the native binary distributions of Perl for Win32, most commonly Strawberry Perl or ActivePerl. Compiling Perl from source code under Windows is possible, but most installations lack the requisite C compiler and build tools. This also makes it difficult to install modules from the CPAN, particularly those that are partially written in C.

ActivePerl is a closed source distribution from ActiveState that has regular releases that track the core Perl releases.[56] The distribution also includes the Perl package manager (PPM),[57] a popular tool for installing, removing, upgrading, and managing the use of common Perl modules.

Strawberry Perl is an open source distribution for Windows. It has had regular, quarterly releases since January 2008, including new modules as feedback and requests come in. Strawberry Perl aims to be able to install modules like standard Perl distributions on other platforms, including compiling XS modules.

The Cygwin emulation layer is another way of running Perl under Windows. Cygwin provides a Unix-like environment on Windows, and both Perl and CPAN are available as standard pre-compiled packages in the Cygwin setup program. Because Cygwin also includes the gcc, compiling Perl from source is also possible.

Database interfaces[]

Perl is widely favored for database applications. Its text-handling facilities are useful for generating SQL queries; arrays, hashes, and automatic memory management make it easy to collect and process the returned data.

In early versions of Perl, database interfaces were created by relinking the interpreter with a client-side database library. This was sufficiently difficult that it was done for only a few of the most-important and most widely used databases, and it restricted the resulting perl executable to using just one database interface at a time.

In Perl 5, database interfaces are implemented by Perl DBI modules. The DBI (Database Interface) module presents a single, database-independent interface to Perl applications, while the DBD (Database Driver) modules handle the details of accessing some 50 different databases; there are DBD drivers for most ANSI SQL databases.

DBI provides caching for database handles and queries, which can greatly improve performance in long-lived execution environments such as mod_perl,[58] helping high-volume systems avert load spikes as in the Slashdot effect.

In modern Perl applications, especially those written using Web application frameworks such as Catalyst, the DBI module is often used indirectly via object-relational mappers such as DBIx::Class, Class::DBI or Rose::DB::Object which generate SQL queries and handle data transparently to the application author.

Comparative performance[]

The Computer Language Benchmarks Game, a project hosted by Alioth, compares the performance of implementations of typical programming problems in several programming languages.[59] The submitted Perl implementations typically perform toward the high end of the memory-usage spectrum and give varied speed results. Perl's performance in the benchmarks game is typical for interpreted languages.[60]

Large Perl programs start more slowly than similar programs in compiled languages because perl has to compile the source every time it runs. In a talk at the YAPC::Europe 2005 conference and subsequent article "A Timely Start", Jean-Louis Leroy found that his Perl programs took much longer to run than he expected because the perl interpreter spent much of the time finding modules because of his over-large include path.[61] Unlike Java, Python, and Ruby, Perl has only experimental support for pre-compiling.[62] Therefore Perl programs pay this overhead penalty on every execution. The run phase of typical programs is long enough that amortized startup time is not substantial, but benchmarks that measure very short execution times are likely to be skewed due to this overhead.

A number of tools have been introduced to improve this situation. The first such tool was Apache's mod_perl, which sought to address one of the most-common reasons that small Perl programs were invoked rapidly: CGI Web development. ActivePerl, via Microsoft ISAPI, provides similar performance improvements.

Once Perl code is compiled, there is additional overhead during the execution phase that typically isn't present for programs written in compiled languages such as C or C++. Examples of such overhead include bytecode interpretation, reference-counting memory management, and dynamic type-checking.


Like any code, Perl programs can be tuned for performance using benchmarks and profiles after a readable and correct implementation is finished. In part because of Perl's interpreted nature, writing more-efficient Perl will not always be enough to meet one's performance goals for a program.

In such situations, the most-critical routines of a Perl program can be written in other languages such as C or Assembler, which can be connected to Perl via simple Inline modules or the more-complex-but-flexible XS mechanism.[63] Nicholas Clark, a Perl core developer, discusses some Perl design trade-offs and solutions in a 2002 document called "When perl is not quite fast enough".[64]

Perl 6[]



Camelia, the logo for the Perl 6 project.[65]

At the 2000 Perl Conference, Jon Orwant made a case for a major new language initiative.[66] This led to a decision to begin work on a redesign of the language, to be called Perl 6. Proposals for new language features were solicited from the Perl community at large, and more than 300 RFCs were submitted.

Larry Wall spent the next few years digesting the RFCs and synthesizing them into a coherent framework for Perl 6. He has presented his design for Perl 6 in a series of documents called "apocalypses", which are numbered to correspond to chapters in Programming Perl. Padron:As of, the developing specification of Perl 6 is encapsulated in design documents called Synopses, which are numbered to correspond to Apocalypses.[67]

Perl 6 is not intended to be backward compatible, although there will be a compatibility mode. Perl 6 and Perl 5 are distinct languages with a common ancestry.[68]

Thesis work by Bradley M. Kuhn, overseen by Larry Wall, considered the possible use of the Java virtual machine as a runtime for Perl.[69] Kuhn's thesis showed this approach to be problematic. In 2001, it was decided that Perl 6 would run on a cross-language virtual machine called Parrot. This will mean that other languages targeting the Parrot will gain native access to CPAN, allowing some level of cross-language development.

In 2005, Audrey Tang created the pugs project, an implementation of Perl 6 in Haskell. This was, and continues to act as, a test platform for the Perl 6 language (separate from the development of the actual implementation) allowing the language designers to explore. The pugs project spawned an active Perl/Haskell cross-language community centered around the freenode #perl6 IRC channel.

A number of features in the Perl 6 language now show similarities to Haskell. Padron:Citation needed

As of 2012, Perl 6 development is primarily centered around two compilers[70], Rakudo Perl 6, an implementation running on top of the Parrot virtual machine, and Niecza, which targets the Common Language Runtime.

Future of Perl 5[]

Development of Perl 5 is also continuing. Perl 5.12.0 was released in April 2010 with some new features influenced by the design of Perl 6.[24][71] Perl 5.14.1 was released on June 17, 2011. Perl 5 development versions are released on a monthly basis, with major releases coming out once per year.[72]

Future plans for Perl 5 include making the core language easier to extend from modules, and providing a small, extensible Meta-object protocol in core.[73]

Perl community[]

Perl's culture and community has developed alongside the language itself. Usenet was the first public venue in which Perl was introduced, but over the course of its evolution, Perl's community was shaped by the growth of broadening Internet-based services including the introduction of the World Wide Web. The community that surrounds Perl was, in fact, the topic of Larry Wall's first "State of the Onion" talk.[74]

State of the Onion[]

State of the Onion is the name for Larry Wall’s yearly keynote-style summaries on the progress of Perl and its community. They are characterized by his hallmark humor, employing references to Perl’s culture, the wider hacker culture, Wall’s linguistic background, sometimes his family life, and occasionally even his Christian background.

Each talk is first given at various Perl conferences and is eventually also published online.

Perl pastimes[]

In email, Usenet, and message board postings, "Just another Perl hacker" (JAPH) programs are a common trend, originated by Randal L. Schwartz, one of the earliest professional Perl trainers.[75] In the parlance of Perl culture, Perl programmers are known as Perl hackers, and from this derives the practice of writing short programs to print out the phrase "Just another Perl hacker,". In the spirit of the original concept, these programs are moderately obfuscated and short enough to fit into the signature of an email or Usenet message. The "canonical" JAPH as developed by Schwartz includes the comma at the end, although this is often omitted.[76]
Perl golf
Perl "golf" is the pastime of reducing the number of characters (key "strokes") used in a Perl program to the bare minimum, much as how golf players seek to take as few shots as possible in a round. The phrase's first use [77] emphasized the difference between pedestrian code meant to teach a newcomer and terse hacks likely to amuse experienced Perl programmers, an example of the latter being JAPHs that were already used in signatures in Usenet postings and elsewhere. Similar stunts had been an unnamed pastime in the language APL in previous decades. The use of Perl to write a program that performed RSA encryption prompted a widespread and practical interest in this pastime.[78] In subsequent years, the term "code golf" has been applied to the pastime in other languages.[79] A Perl Golf Apocalypse was held at Perl Conference 4.0 in Monterey, California in July 2000.
As with C, obfuscated code competitions were a well known pastime in the late 1990s. The Obfuscated Perl Contest was a competition held by The Perl Journal from 1996 to 2000 that made an arch virtue of Perl's syntactic flexibility. Awards were given for categories such as "most powerful"—programs that made efficient use of space—and "best four-line signature" for programs that fit into four lines of 76 characters in the style of a Usenet signature block.[80]
Perl poetry is the practice of writing poems that can be compiled as legal Perl code, for example the piece known as Black Perl. This hobby is made possible by the large number of English words that are used in the Perl. New poems are regularly submitted to the community at PerlMonks.[81]

Perl on IRC[]

There are a number of IRC channels that offer support for the language and some modules.

IRC Network Channels #perl #perl6 #cbstream #perlcafe #poe #moose #poe #catalyst #dbix-class #perl-help #distzilla #epo #corehackers #sdl #win32 #toolchain #padre #perlmonks #perl #perlhelp #perl #debian-perl

CPAN Acme[]

There are also many examples of code written purely for entertainment on the CPAN. Lingua::Romana::Perligata, for example, allows writing programs in Latin.[82] Upon execution of such a program, the module translates its source code into regular Perl and runs it.

The Perl community has set aside the "Acme" namespace for modules that are fun in nature (but its scope has widened to include exploratory or experimental code or any other module that is not meant to ever be used in production). Some of the Acme modules are deliberately implemented in amusing ways. This includes Acme::Bleach, one of the first modules in the Acme:: namespace,[83] which allows the program's source code to be "whitened" (i.e., all characters replaced with whitespace) and yet still work.

See also[]


  • Outline of Perl
  • Perl language structure
  • Perl Data Language
  • Perl Object Environment
  • Plain Old Documentation



Further reading[]

  • Learning Perl 6th Edition (2011), O'Reilly. Beginner-level introduction to Perl.
  • Modern Perl 2nd Edition (2011-2012), Onyx Neon. Describes Modern Perl programming techniques.
  • Programming Perl 4th Edition (2012), O'Reilly. The definitive Perl reference.
  • Perl Cookbook, ISBN 0-596-00313-7. Practical Perl programming examples.
  • Padron:Cite book Functional programming techniques in Perl.

External links[]

Padron:Sister project links

Padron:Perl Padron:FOSS

Padron:Link GA

als:Perl ar:بيرل bn:পার্ল (প্রোগ্রামিং ভাষা) zh-min-nan:Perl bg:Пърл (език за програмиране) bs:Perl ca:Perl cs:Perl cy:Perl (cyfrifiadureg) da:Perl pdc:Perl de:Perl (Programmiersprache) et:Perl el:Perl es:Perl eo:Perl eu:Perl fa:پرل (زبان برنامه‌نویسی) fr:Perl (langage) ga:Perl gl:Perl gu:પર્લ ko:펄 hi:पर्ल hr:Perl id:Perl it:Perl he:Perl ka:პერლი ku:Perl la:Perl lv:Perl lb:Perl (Programméiersprooch) lt:Perl hu:Perl (programozási nyelv) mk:Perl ml:പേള്‍ mr:पर्ल (संगणकभाषा) ms:Perl my:Perl nl:Perl (programmeertaal) ja:Perl no:Perl nn:Perl pl:Perl pt:Perl ro:Perl ru:Perl sah:Perl sq:Perl simple:Perl sk:Perl sl:Perl ckb:پێرڵ (وێب داڕشتن) sr:Перл (програмски језик) sh:Perl fi:Perl sv:Perl ta:பெர்ள் th:ภาษาเพิร์ล tg:Перл (забони барномасозӣ) tr:Perl uk:Perl ur:Perl vi:Perl bat-smg:Perl zh:Perl

Sourced Reference lifted electronically from the internet from Webaddress:


Angmayakda 18:23, Abril 17, 2012 (UTC)

  1. Padron:Cite web
  2. Padron:Cite web
  3. Padron:Cite web
  4. Padron:Cite web
  5. 5.0 5.1 5.2 5.3 Padron:Cite book
  6. Padron:Cite book
  7. Padron:Cite web
  8. Padron:Cite web Padron:Dead link
  9. Padron:Cite web
  10. Padron:Cite web
  11. Padron:Cite web
  12. Padron:Cite web
  13. 13.0 13.1 Padron:Cite web
  14. Padron:Cite book
  15. Padron:Cite web
  16. Padron:Cite web
  17. Padron:Cite web
  18. Padron:Cite web
  19. Padron:Cite web
  20. Padron:Cite web
  21. Padron:Cite web
  22. Padron:Cite web
  23. Padron:Cite web
  24. 24.0 24.1 Padron:Cite web
  25. Padron:Cite web
  26. 26.0 26.1 Padron:Cite web
  27. 27.0 27.1 Padron:Cite web
  28. Padron:Cite web
  29. Steve McConnell (2004) Code Complete, 2nd ed., Microsoft Press, p. 65.
  30. Padron:Cite web
  31. Padron:Cite web
  32. 32.0 32.1 Padron:Cite book
  33. 33.0 33.1 Padron:Cite web
  34. Padron:Cite web
  35. Padron:Cite news
  36. Padron:Cite web
  37. Usenet post, May 10, 1997, with ID
  38. Padron:Cite web
  39. Padron:Cite web
  40. Padron:Cite web
  41. Padron:Cite web
  42. Padron:Cite book
  43. Padron:Cite web
  44. Padron:Cite web
  45. Padron:Cite web
  46. A description of the Perl 5 interpreter can be found in Programming Perl, 3rd Ed., chapter 18. See particularly page 467, which carefully distinguishes run phase and compile phase from run time and compile time. Perl "time" and "phase" are often confused.
  47. Padron:Cite web
  48. Padron:Cite web
  49. Padron:Cite web
  50. Padron:Cite journal and Padron:Cite journal, available online at Padron:Cite web
  52. Padron:Cite web
  53. Padron:Cite web
  54. Padron:Cite web
  55. Padron:Cite web
  56. Padron:Cite web
  57. Padron:Cite web
  58. Padron:Cite web
  59. Padron:Cite web
  60. Padron:Cite web
  61. Padron:Cite web
  62. Padron:Cite web
  63. Padron:Cite web Padron:Dead link
  64. Padron:Cite web
  65. Padron:Cite web
  66. Padron:Cite web
  67. Padron:Cite web
  68. Padron:Cite web
  69. Padron:Cite journal
  70. Padron:Cite web
  71. Padron:Cite web
  72. Padron:Cite web
  73. Padron:Cite web
  74. Padron:Cite web
  75. Padron:Cite newsgroup
  76. Padron:Cite web
  77. Padron:Cite newsgroup
  78. Padron:Cite web
  79. Padron:Cite web
  80. Padron:Cite book
  81. Padron:Cite web
  82. Padron:Cite web
  83. Padron:Cite web