Difference between revisions of "Perl"
Jump to navigation
Jump to search
m (post-import navbar cleanup; rewrote intro; added error-handling question) |
|||
| Line 1: | Line 1: | ||
| − | {{ | + | {{seed}}[[Computing]]: [[Programming]]: [[Perl]] |
| − | [[ | ||
| − | [[ | ||
| − | + | [[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 [[Perl regex|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== | ==Articles== | ||
| Line 12: | Line 10: | ||
==Libraries and Modules== | ==Libraries and Modules== | ||
*[http://search.cpan.org/ CPAN]: search the Comprehensive Perl Archive Network | *[http://search.cpan.org/ 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). | ||
Revision as of 21:43, 14 October 2005
|
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
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).