Best Practices Book, Document, Web Site?
in [General]
|
Prev: mysqli_connect problem
Next: gentoo php
From: "Hansen, Mike" on 1 Mar 2010 15:48 Is there a PHP Best Practices Book, Document, or web site that has information similar to Perl Best Practices but for PHP?
From: Shawn McKenzie on 1 Mar 2010 18:08 Hansen, Mike wrote: > Is there a PHP Best Practices Book, Document, or web site that has information similar to Perl Best Practices but for PHP? > I'm not familiar with the Perl one, so I don't know specifically what you mean, but there are many "coding standards". Probably the Zend one would be the closest: http://framework.zend.com/manual/1.10/en/coding-standard.overview.html -- Thanks! -Shawn http://www.spidean.com
From: "pan" on 1 Mar 2010 22:54 ""Hansen, Mike"" <Mike.Hansen(a)atmel.com> wrote in message news:7941B2693F32294AAF16C26B679A258D0EFDC318(a)csomb01.corp.atmel.com... Is there a PHP Best Practices Book, Document, or web site that has information similar to Perl Best Practices but for PHP? Yeah, it's hard to find this stuff. A google search on {+"Best Practices" +"PHP"} returned only 4,340,000 hits. Maybe, some day, someone will think to write something up. Good luck.
From: Rene Veerman on 2 Mar 2010 00:24 http://oreilly.com/php/index.html perhaps? I dont know any free online best practice docs (other than the php.net function comments) that sum it all up nicely. But best practices are like coding standards; there are at least a few that are (near-)equals. Personally, the basis of my current coding style is as such: - hungarianCasingConventionWithAbbreviationsWTFlikeSo - almost always short names for variables in simple code < 40 lines - almost always longer and descriptive names for more complicated code. - usually short comments: explanations for noobs (to problem area) - the rest of the "commenting" is done by the code using descriptive var & function names (last 3 points makes for "self-documented code") - consolidate all logic in the script, so use specific sets (_POST/_GET) rather than generic sets (_REQUEST) - document it in script if behaviour is dependent on outside sources (like php.ini) - use of "config.php" in project rootdir to set DEFINE()s and any global variables. - use of adodb.sf.net for database abstraction. - use a standarized directory structure for all php projects; /project/.htaccess - RewriteRule -> php scripts /project/php - all php scripts /project/js - all javascript, including .js.php /project/lib/component-x.y.z/ - all 3rd party libraries, regardless of language, x.y.z=versionnum /project/sql - sql init / maintenance scripts (possibly) /project/theme/themeName/many.css(.php) (or:) /project/css/some.css(.php) (possibly:) /project/admin/ - use of an error handler that knows when to mail errors to developer, when to print errs in browser and when not to, etc. a "proper error handler". mine is still evolving. - use of a standard debug output lib, called by a function that checks config.php for a DEBUG_MODE define. prevents production machines from showing debug info. plug: my free http://mediabeez.ws/htmlMicroscope/ is kinda nice. - push all input into DB through functions that prevent SQL insertion (at least a filter through mysql_real_escape) and HTML/js/flash/etc insertions (harder). - an authentication scheme that can be called with simple functions, but which also does checks on whether or not the IP that started the session is the same as the IP making a request on a certain session. - calling of the authentication scheme by nearly all scripts - in any lenghty operation, design for continuation of the operation when a given item fails. example from OS file copiers: it stops when it needs to ask a question. i rather design to "keep going", log all items that require user interaction, and let the user deal with them when he/she has time. there's probably more that would make it into my best practices list, but i'm gonna leave it at this for now.. On Mon, Mar 1, 2010 at 9:48 PM, Hansen, Mike <Mike.Hansen(a)atmel.com> wrote: > Is there a PHP Best Practices Book, Document, or web site that has information similar to Perl Best Practices but for PHP? > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >
From: Paul M Foster on 2 Mar 2010 09:44
On Mon, Mar 01, 2010 at 01:48:14PM -0700, Hansen, Mike wrote: > Is there a PHP Best Practices Book, Document, or web site that has information similar to Perl Best Practices but for PHP? FWIW, we tried to create a thread to gather these "best practices" ideas, and mostly what we got was arguments from people who took exception one way or another. Paul -- Paul M. Foster |