At 5/2/2001 12:46 PM, Anuradha Ratnaweera wrote:
>Most of your guidelines match with our practices. Here are some comments.
Thanks for the comments.
> > 1.4 Whitespaces
> >
> > - No whitespace after function or method name. Example:
> >
> > exit()
>
>We also use this. But I have s
Most of your guidelines match with our practices. Here are some comments.
On Sat, 28 Apr 2001, Steven Haryanto wrote:
> 0.1 We are writing PHP4 application here, not PHP3, nor Perl, Python, etc.
> So use PHP idioms.
Same here.
> 0.3 Consistency matters.
>
> 0.4 Standards is important.
>
lass.php and filename.lib.php, only contain functions,
classes, variable declarations, etc.
--Toby
- Original Message -
From: "Johnson, Kirk" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 30, 2001 6:22 PM
Subject: RE: [PHP] Please review our coding s
; Subject: [PHP] Please review our coding standards [ ideas ]
> 4. File organization
>
> 4.2 All PHP libraries and include files, is named with '.php'
> extension (ie.
> no '.lib', '.inc', etc.). Test scripts is named with
Dear folks,
I am composing a coding standards for our team. Bottom line, we are
using PEAR, object-oriented programming, extreme programming, and
PHPDoc. Below is the draft so far. I'd greatly appreciate it if
anybody care to give inputs on the document. Nevertheless, I hope
this could be useful
5 matches
Mail list logo
