|
|
Posted by Shelly on 11/09/07 02:45
larry@portcommodore.com wrote:
> As a solo coder for many years I've evolved before PHP in cleaning up
> some of my coding practices (when you have 10+ years of code to
> maintain you learn the hard way the importance of good coding
> practices. Since starting PHP I've adopted many PHP coding guidelines
> for formatting etc.
>
> It makes life a lot easier to have well formatted code, in debugging
> you will know where you are in a decision process or a loop, and a
> couple years down the road the formatting variable/function naming and
> comments will save you a lot of time getting back up to speed when you
> revisit your old code.
>
> I use a lot of Pear formatting guidelines for my code - I don't use
> Pear but a lot of their guidelines are very common sense stuff. And
> if I ever do at least I'm part way there.
>
> have a look and see what you think:
> http://www-eleves-isia.cma.fr/documentation/PhpDoc/pear.standards.html
>
> Larry
I like the Java naming conventions. I also like K&R block structure for
braces. I use two space tabs. I also put a space before and after an
equals sign or logical operations or concatenation operators. Names should
ALWAYS be meaningful. In multiple condition conditionals I put each
condition in its own parentheses. Also, I like to keep file short. If
there are several operations that are sizable, I will put each in a separate
file (with a good name) and use a require statement. These are a few of the
things I have adopted over the years and it has paid off as both a lone
programmer and as part of a group.
--
Shelly
Navigation:
[Reply to this message]
|