"Jeff Oien" [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Would people like to list bad practices and also point us
newbies to any articles online dealing with syntax, correct
use of single and double quotes etc.?
People who create scripts that include a
"Jeff Oien" [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Would people like to list bad practices and also point us
newbies to any articles online dealing with syntax, correct
use of single and double quotes etc.?
People who create scripts that include a
Which is why anyone with a clue makes any special extensions they use
protected by the web server. Which is why I protect .inc, .cfg, .class,
etc. It's also a good idea not to store config-type files in the web tree.
Rick Hodger wrote:
"Jeff Oien" [EMAIL PROTECTED] wrote in message
[EMAIL
Hodger [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 14. Februar 2001 09:51
An: [EMAIL PROTECTED]
Betreff: Re: [PHP] Bad Practices
"Jeff Oien" [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Would people like to list bad practices
Three good articles by the author of PHP Developer's Cookbook.
Top 21 PHP progamming mistakes
By Sterling Hughes
http://zend.com/zend/art/mistake.php
http://zend.com/zend/art/mistake1.php
http://zend.com/zend/art/mistake2.php
-Ben Munoz
-Original Message-
From: Jeff Oien
Be sure to check this out :
Using Strings :
---
http://www.zend.com/zend/tut/using-strings.php
Don't put large blocks of HTML within echo or print, don't be afraid
to escape out of PHP for that.
From: "Philip Olson" [EMAIL PROTECTED]
They're very useful. Also, regarding SQL, don't do "SELECT * ..." all the
time as it's overkill if not all fields are being used.
And, in fact, doing a "SELECT *" ends up precluding most optimizations
within a query engine! Selecting only what you really
7 matches
Mail list logo
