Perl: Difference between revisions
from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
m →Questions: code from Tene |
m →Articles: link to vs php article |
||
| Line 4: | Line 4: | ||
==Articles== | ==Articles== | ||
*[[Perl built-in functions]] | ===Usage=== | ||
*[[Perl regex]] | * [[Perl built-in functions]] | ||
* [[Perl regex]] | |||
===Design=== | |||
* [[Perl vs. PHP]] | |||
==Other Documentation== | ==Other Documentation== | ||
*[http://www.cpan.org/ CPAN]: documentation links at the Comprehensive Perl Archive Network | *[http://www.cpan.org/ CPAN]: documentation links at the Comprehensive Perl Archive Network | ||
Revision as of 01:49, 27 February 2006
<hide>
page status::seed
</hide>
|
This page is a seed article. You can help HTYP water it: make a request to expand a given page and/or donate to help give us more writing-hours!
|
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
Design
Other Documentation
- CPAN: documentation links at the Comprehensive Perl Archive Network
Libraries and Modules
- CPAN: search the Comprehensive Perl Archive Network
Questions
- Is it possible to intercept errors in Perl? This is especially critical when developing web applications, as a crashed Perl program will return a failure code to the web server (usually Apache), causing either a "500 Internal Server" error due to "premature end of script headers" or else a truncation of the output (with no apparent cause). Tracing these errors is especially difficult since Perl has no block-comment syntax (that I know of). Follow-up: this would seem to be a guide to exception-handling in Perl. Also this. And this: "use CGI::Carp qw(fatalsToBrowser);"
