perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Shiflett <shifl...@php.net>
Subject Re: Why I use mod_perl (PR stuff)
Date Wed, 09 Jun 2004 20:42:20 GMT
--- James G Smith <JGSmith@TAMU.Edu> wrote:
> PHPUnit is available, first release was April, 2002.  First
> production release was mid-March, 2004.

I didn't say this stuff was old or mature, just that it exists. :-) Truly,
PHP feels like it is just now reaching the maturity level that Perl
enjoyed as much as 10 years ago or more. Of course, Perl is much older, so
this is to be expected somewhat.

> Didn't find anything for `embedded documentation'

There is PHPDoc, which is basically the same thing as JavaDoc. Perl's
options may be much better, but you can poke around on a site that uses
PHPDoc here:

http://developer.blueshoes.org/phpdoc/

> Didn't find anything that indicated I could choose to require
> variable declarations before referencing them.

PHP handles this sort of thing with error reporting. A reference to an
undefined variable throws a notice, and by default, PHP's error reporting
doesn't alert you to notices (only warnings and above).

A common recommendation is to develop with error_reporting set to E_ALL,
and display_errors enabled (and of course to initialize all variables).
Then, in production, log errors instead of display them (or in PHP 5, set
up a more professional system altogether). At any rate, using E_ALL is
basically the same thing as use strict.

Chris

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html


Mime
View raw message