On Thursday 19 April 2001 22:31, you wrote:
Definitely the second style :)
(If we were talking about C(++) then the first would have even been
forbidden by my companies coding standard as well as several coding
standards of other companies I worked for.)
put_on item='asbestos battle armor'
On Thursday 19 April 2001 21:48, Steve Lawson wrote:
Personally, I hate trailing {'s
Personally, I hate having the {'s on the next line. I always trail them in
others code when they have them on the next line :)
and there are thousand of ways that the people here displays textblocks. some
On Thursday 19 April 2001 19:57, you wrote:
Which is better?
function blah() {
switch( $bob ) {
case 1:
return "this";
function blah() {
$retval = "";
switch( $bob ) {
case 1:
$retval = "this";
break;
In other words, is it good practice to exit
i say the first style.
unneeded variables and other thingies just
obscure things and make it harder to maintain.
-Original Message-
From: Boget, Chris [mailto:[EMAIL PROTECTED]]
Subject: [PHP] Which is better coding style...
Which is better?
function blah() {
switch( $bob )
Personally, I hate trailing {'s
I think this
function blah()
{
switch( $bob )
{
case 1:
$var = "whatever";
break;
}
}
Is much easier to read and follow. As for the exiting question...
The "proper" way is to use the breaks. "They" say that multiple returns in
etval = "other";
break;
}
return $retval;
}
-Original Message-
From: ..s.c.o.t.t.. [gts] [mailto:[EMAIL PROTECTED]]
Sent: 19 April 2001 21:31
To: Php-General
Subject: RE: [PHP] Which is better coding style...
i say the first style.
unneeded variables and othe
On Jue 19 Abr 2001 23:35, Miles Thompson wrote:
Amen! For both elimination of trailing {'s , and a good clear break.
I don't know how trailing {'s came about, but I find the blocks are harder
to follow. I consider them HIDDEN rather than trailing, but I cut my teeth
on Pascal, and FoxPro.
Amen! For both elimination of trailing {'s , and a good clear break.
I don't know how trailing {'s came about, but I find the blocks are harder
to follow. I consider them HIDDEN rather than trailing, but I cut my teeth
on Pascal, and FoxPro. While we're at it, how about plain old carriage
nder Pilon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 19, 2001 4:32 PM
To: 'Php-General'
Subject: RE: [PHP] Which is better coding style...
Definitely the second style :)
(If we were talking about C(++) then the first would have even been
forbidden by my companies coding standa
Hi,
This participates the clearest for me,
but unfortunately not usual.
if (...)
{...commands...
switch(...)
{case commands...
case commands...
case commands...
}
while(...)
{...commands...
}
}
else
{...commands...
coding style? here's what pear has to say :
http://www.php.net/manual/en/pear.standards.php
http://www.php.net/manual/en/pear.standards.control.php
[ example ]
switch (condition) {
case 1:
action1;
break;
case 2:
action2;
break;
default:
On 19 Apr 2001 14:08:13 -0700, ..s.c.o.t.t.. [gts] [EMAIL PROTECTED]
wrote:
OOooo...
it drives me nuts when i see beginning brackets
on seperate lines ;)
i like to start brackets on the same line as the
statement and finish them on a line of their own.
Very strong agreement here. I think a lot
Your coding style is not the most used..
But I must be honest and tell you that I also find the clearest way...
I also use it on all my own code.. It has got the advantage that you always
see all brackets (no need to scroll to the right to find a bracket) and if
you go down on the same
nuts to see "} else {" also)
-Original Message-
From: Sander Pilon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 19, 2001 4:32 PM
To: 'Php-General'
Subject: RE: [PHP] Which is better coding style...
Definitely the second style :)
(If we were talking about C(+
I preffer the first.
--
Chris Lee
[EMAIL PROTECTED]
""Boget, Chris"" [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Which is better?
function blah() {
switch( $bob ) {
case 1:
return "this";
case 2:
return "that";
default:
r";
break;
}
return $retval;
}
-Original Message-
From: ..s.c.o.t.t.. [gts] [mailto:[EMAIL PROTECTED]]
Sent: 19 April 2001 21:31
To: Php-General
Subject: RE: [PHP] Which is better coding style...
i say the first style.
unneeded variables and other thingies just
I would like to see an editor with a built in code beutifier and un-beutifier. I like
the
if (true)
{
} else
{
}
method, but pear standards are
if (true) {
} else {
}
it would be nice to see ultra edit convert it to the first format for me and save it
as the second for pear.
--
- Original Message -
From: Chris Lee [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 19, 2001 3:51 PM
Subject: Re: [PHP] Which is better coding style...
I would like to see an editor with a built in code beutifier and
un-beutifier. I like the
if (true)
{
}
Message-
From: ..s.c.o.t.t.. [gts] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 19, 2001 2:05 PM
To: Php-General
Subject: RE: [PHP] Which is better coding style...
OOooo...
it drives me nuts when i see beginning brackets
on seperate lines ;)
i like to start brackets on the same line
19 matches
Mail list logo
