Difference between revisions of "Perl"
Jump to navigation
Jump to search
(→Libraries and Modules: perldbi) |
m (→Libraries and Modules: perl dbi local article) |
||
Line 17: | Line 17: | ||
** [http://search.cpan.org/ CPAN]: search the Comprehensive Perl Archive Network | ** [http://search.cpan.org/ CPAN]: search the Comprehensive Perl Archive Network | ||
* '''Frequently-used libraries''': | * '''Frequently-used libraries''': | ||
− | ** [ | + | ** [[Perl DBI]]: database interface |
==Notes== | ==Notes== |
Revision as of 23:45, 29 June 2006
computing: software: programming: Perl
Overview
Perl is a programming language widely used for web sites and Linux servers. It can be somewhat baffling to the eye – largely due to the frequent use of regular expressions – but due to its popularity it has been greatly refined and there is a large base of existing code available for reuse.
Articles
Usage
- Perl reference
- Perl built-in functions
- Perl regex
- official documentation
Design
Other Documentation
- CPAN: documentation links at the Comprehensive Perl Archive Network
Libraries and Modules
- Collections:
- CPAN: search the Comprehensive Perl Archive Network
- Frequently-used libraries:
- Perl DBI: database interface
Notes
- Although single-quoted strings are widely cited as not interpreting anything, you do have to backslash certain characters if you want them represented literally:
- the single-quote itself ( \' )
- period ( \. )
- One of the reasons for PHP's popularity over Perl for developing web applications is that it prints errors to the web browser, rather than simply quitting abruptly (causing either an incomplete page or, more likely, a 5xx Server Error). Perl does not do this by default. It is, however, quite easy to make this happen, by including the following line of code near the beginning of a program:
use CGI::Carp qw(fatalsToBrowser);
- Although there is apparently no formal block-quote syntax (like /* */ in c/c++), a syntax used for documentation seems to accomplish the same thing. It's not presently known whether this is documented anywhere. "=anystring", at the beginning of a line, starts a block comment, and "=cut" at the beginning of a line ends the comment. This has not been tested thoroughly, but the exact string "cut" does seem to be necessary. Example:
regular_code_here(); ==something This part is commented, i.e. ignored by the parser. Anything up until the "cut" line. ==cut more_code();