Re: [PHP] Coding Standards Document

On Wednesday 22 November 2006 16:31, tedd wrote: > At 7:14 PM -0500 11/21/06, Robert Cummings wrote: > >On Tue, 2006-11-21 at 16:19 -0500, tedd wrote: > >> It seems that every time I ask a security question, I find that I'm > >> currently practicing the answers to avoid the pit-falls. > > > >Exce

Re: [PHP] Coding Standards Document

On Wed, 2006-11-22 at 10:31 -0500, tedd wrote: > At 7:14 PM -0500 11/21/06, Robert Cummings wrote: > >On Tue, 2006-11-21 at 16:19 -0500, tedd wrote: > >> It seems that every time I ask a security question, I find that I'm > >> currently practicing the answers to avoid the pit-falls. > > > >Except

Re: [PHP] Coding Standards Document

At 7:14 PM -0500 11/21/06, Robert Cummings wrote: On Tue, 2006-11-21 at 16:19 -0500, tedd wrote: It seems that every time I ask a security question, I find that I'm currently practicing the answers to avoid the pit-falls. Except that one time when his site got defaced... that was news ;) ;)

Re: [PHP] Re: PHP Coding Standards

On 02/06/2004, at 3:00 AM, Justin Patrin wrote: And I'm one of them. :-) I like the K&R version because it saves verticaly space and most editors can't really handle correct tabbing when you put it after. IMHO it's just not necessary as ALL blocks should have braces, even those that are one-line

Re: [PHP] Re: PHP Coding Standards

Travis Low wrote: Justin Patrin wrote: Travis Low wrote: [I hate K&R indenting] And I'm one of them. :-) I like the K&R version because it saves verticaly space and most editors can't really handle correct tabbing... Arrggghh...TABS. Don't even get me started on tabs... cheers, Travis I meant

RE: [PHP] Re: PHP Coding Standards

[snip] >> [I hate K&R indenting] > > And I'm one of them. :-) I like the K&R version because it saves > verticaly space and most editors can't really handle correct tabbing... Arrggghh...TABS. Don't even get me started on tabs... [/snip] How many holy wars can be started in one thread legally

Re: [PHP] Re: PHP Coding Standards

Justin Patrin wrote: Travis Low wrote: [I hate K&R indenting] And I'm one of them. :-) I like the K&R version because it saves verticaly space and most editors can't really handle correct tabbing... Arrggghh...TABS. Don't even get me started on tabs... cheers, Travis -- Travis Low

Re: [PHP] Re: PHP Coding Standards

Travis Low wrote: I have to say I like everything about the PEAR coding standards except for the K&R bracing style. I much prefer: if( foo ) { blah; } to if( foo ) { blah; } The latter form (K&R) conserves vertical space, but I find it a lot harder to follow. Harder to move

Re: [PHP] Re: PHP Coding Standards

On 31-May-2004 Travis Low wrote: > I have to say I like everything about the PEAR coding standards > except for the > K&R bracing style. I much prefer: > >if( foo ) >{ > blah; >} > Icky. So ... Vee-Eye or Eighty Megs and Constantly Swapping ? ;-> -- Don Read

Re: [PHP] Re: PHP Coding Standards

"Travis Low" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I have to say I like everything about the PEAR coding standards except for the > K&R bracing style. I much prefer: > >if( foo ) >{ > blah; >} > > to > >if( foo ) { > blah; >} > > > The latter

Re: [PHP] Re: PHP Coding Standards

I have to say I like everything about the PEAR coding standards except for the K&R bracing style. I much prefer: if( foo ) { blah; } to if( foo ) { blah; } The latter form (K&R) conserves vertical space, but I find it a lot harder to follow. Harder to move blocks of code ar

[PHP] Re: PHP Coding Standards

charles kline wrote: Hi all, I was having a conversation with a friend and talking about coding standards in the open source community (focusing on PHP). I seem to remember there being a document out there that sort of laid it out pretty well. Anyone know where I might find a copy? PEAR has a p

Re: [PHP] PHP Coding Standards

On Saturday 29 May 2004 08:55 am, charles kline wrote: > Hi all, > > I was having a conversation with a friend and talking about coding > standards in the open source community (focusing on PHP). I seem to > remember there being a document out there that sort of laid it out > pretty well. > > Anyon

[PHP] PHP Coding Standards

Hi all, I was having a conversation with a friend and talking about coding standards in the open source community (focusing on PHP). I seem to remember there being a document out there that sort of laid it out pretty well. Anyone know where I might find a copy? Thanks, Charles -- PHP General Ma

Re: [PHP] coding standards - control structures

]> > To: <[EMAIL PROTECTED]> > Sent: Friday, September 27, 2002 2:16 PM > Subject: [PHP] coding standards - control structures > > > > Hey all. I've read the pear coding standards. > > I assume that if php has any official coding > standards > >

Re: [PHP] coding standards - control structures

Sent: Friday, September 27, 2002 2:40 PM Subject: Re: [PHP] coding standards - control structures > Kevin Stone wrote: > > > > I believe the standards are for coding PEAR modules so all code is presented > > in the same style. It really has no influence on the language or commun

Re: [PHP] coding standards - control structures

Kevin Stone wrote: > > I believe the standards are for coding PEAR modules so all code is presented > in the same style. It really has no influence on the language or community > at large. I say code the way you feel most comfortable with and damb to > anyone who complains. :) > -Kevin The be

Re: [PHP] coding standards - control structures

: "ed" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 27, 2002 2:16 PM Subject: [PHP] coding standards - control structures > Hey all. I've read the pear coding standards. > I assume that if php has any official coding standards > > then th

[PHP] coding standards - control structures

Hey all. I've read the pear coding standards. I assume that if php has any official coding standards then the pear standards would be them, correct? Anyways, the pear docs on coding standards show examples of using controls structures like the following: if ( !$var ) { do_something(); }

[PHP] coding standards

Ive read through the PEAR coding standards but was wondering about a few things not talked about in them - - Is declaring all variables a good idea - so theres no unassigned variables hanging around ? (no warnings produced when error reporting set to E_ALL) - Naming of include files - .inc or .ph