Ede,
I have been through this many times on commercial and other projects and
have found that developers (myself included) get very upset around
coding standards. I have also found that projects work much better if
someone within the project makes a decision and provides a documented
standard
this should read:
finally I think this can go much to far, there is a potential risk to loose
development capacities here, just because of indifferences about
styling... keeping it balanced should be the way.
regards ede
--
> The important thing about using the SAME style is that if I am
> ex
I agree on that ... style in terms of layout especially for easier diff
detection is important..
style in terms of syntax for easier debugging. I also agree on that.
But: If I decide to use ?: for my extension, people working on it _have
to_ learn this perfectly legal and short statement, I am so
The important thing about using the SAME style is that if I am extending
someone else's code in the same project (e.g. adding an additional else
if clause) that when I do a diff I can see oh I just added a diff
clause, rather than, oh there are abunch of whitespace changes so I
really have no w
Yes, but I don't believe that would add anything to readability...
I think the key is not about everybody using the same style,
but about each one using a "consistent" style.
If one always use the same style, even a non-programmer it's perfectly able
of understanding it after a couple of exampl
