RE: Fw: [PHP] debuging and getting mor information about failures

> -Original Message- > From: Chris W. Parker [mailto:[EMAIL PROTECTED] > Sent: 29 July 2003 19:22 > To: Ford, Mike [LSS]; Gabriel Guzman; Peter James > Cc: [EMAIL PROTECTED] > Subject: RE: Fw: [PHP] debuging and getting mor information about > failures > > >

Re: Fw: [PHP] debuging and getting mor information about failures

* Thus wrote Jay Blanchard ([EMAIL PROTECTED]): > [snip] > I wonder why the heck the author didn't just go for the alternative > syntax with proper end-tokens and get the added value they deliver. > [/snip] > > At the risk of stepping of of the curb into the holy-war that rages > about this the an

RE: Fw: [PHP] debuging and getting mor information about failures

Ford, Mike on Tuesday, July 29, 2003 11:00 AM said: > I know the braces vs. end-token debate is almost on the scale of a > holy war, and I admit to hating the curly-brace style with a passion, > but when I see code like this: > > function doit() > { > for() > { >

Re: Fw: [PHP] debuging and getting mor information about failures

> I know the braces vs. end-token debate is almost on the scale of a holy war, > and I admit to hating the curly-brace style with a passion, but when I see code > like this: [snip code] Yeah, I'd hate curly braces with a passion if I saw code like that, too. How can anyone *possibly* read that

RE: Fw: [PHP] debuging and getting mor information about failures

[snip] I wonder why the heck the author didn't just go for the alternative syntax with proper end-tokens and get the added value they deliver. [/snip] At the risk of stepping of of the curb into the holy-war that rages about this the answer Mike is that a lot of PHP coders are what as known as "ol

RE: Fw: [PHP] debuging and getting mor information about failures

> -Original Message- > From: Chris W. Parker [mailto:[EMAIL PROTECTED] > Sent: 29 July 2003 17:56 [...snip...] > As opposed to the much easier to read (and line up curly > braces) method: > > function doit() > { > for() > { > if() > } >

RE: Fw: [PHP] debuging and getting mor information about failures

Gabriel Guzman on Tuesday, July 29, 2003 9:44 AM said: > A tip on avoiding errors cause by not enough }'s is to close any > bracket immediately after you open it, so if I were writing a block > of code: Good tip. I do this too. > I would write the above first, and

Re: Fw: [PHP] debuging and getting mor information about failures

A tip on avoiding errors cause by not enough }'s is to close any bracket immediately after you open it, so if I were writing a block of code: function foo(){ } I would write the above first, and then fill in between the {}'s. This way, when I get to the end of my script, I know I'm at least not

Fw: [PHP] debuging and getting mor information about failures

Just forwarding this reply back to the list. - Original Message - From: "Chris W. Parker" <[EMAIL PROTECTED]> To: "Peter James" <[EMAIL PROTECTED]> Sent: Tuesday, July 29, 2003 10:26 AM Subject: RE: [PHP] debuging and getting mor information about failures Peter James