Paul M Jones wrote:
Jeff Moore wrote:
Having your code in a "normalized" form frees the mind to consider
other aspects of the code. Poorly or inconsistently styled code can
obscure refactorings. With a good coding standard, the benefits
outweigh having to re-train yourself out of a few habits.
The general thesis is to adopt a previously-existing published
standard (in this case, PEAR) and adhere to it, noting any deviations
as exceptions. See also the Solar coding style guide, which is
composed only of a link to the PEAR style guide and one exception note.
The flaw in this thinking is that "normalized" code does not "free the
mind" if the formatting is not what you use. There are those who like
more vertical space and those who do not. There is not understanding
between the two groups because their brains simple prefer different
things. And programmers more than any group can rationalize either position.
I think what we really need is flexibility, not rigidity, to things as
trivial a spacing. It is Good Software Design, not formatting, that
truly frees the mind.
I think that rather than forcing half the group to conform -- we should
all of us become more flexible. That flexibility may also improve our
designs and communication. I say allow flexibility in braces for ZF
developers. I find both K&R or BSD style braces are perfectly readable.
I think transcending "bracism" would be an important statement of
maturity for this framework.
