play. I don't know
| you well enough to have formed any opinion.
It looked to me like you did.. if you didn't, fine. :)
| Everybody is of course free to write in whatever arcane style they
| want, as long as the *checked in code* complies with the mandated
| coding style!
|
| Is this your idea
On Sun, Nov 03, 2002 at 05:27:19PM -0800, Robin Rowe wrote:
Martin,
Everybody is of course free to write in whatever
arcane style they want, as long as the *checked in code* complies with
the mandated coding style!
Is this your idea of being broadminded? To reject contributions? Or, do
Hi. It is easy for coding style to spark a religious war, and I'm not
interested in futile debate. So please bear in mind that my comments are my
observations, not a call-to-arms.
Coding style is motivated by important but incompatible goals.
1. Readability of the code
2. Compatibility
reasons to desire coding style, but sometimes it is about
power. The third goal, listed but not presumed here, is to have an excuse to
interfere.
Oh please. I asked Tollef to set up some kind of guidelines, and I had
to ask him several times to get him to do it ;) I didn't want to do it
as I'm
, it indents correctly.
| There are good reasons to desire coding style, but sometimes it is about
| power. The third goal, listed but not presumed here, is to have an excuse to
| interfere.
yeah, sure. It's because I want utter and full control of the
installer, because I'm some power-hungry
style they want, as long as the *checked in code* complies with
the mandated coding style!
Is this your idea of being broadminded? To reject contributions? Or, do you
have a different point? Are you volunteering to do the work of reformating
all checked in code for consistency no matter what style
Is there a particular coding style which people prefer?
So far, I've seen both
int main(int argc, char **argv) {
and
static int debconfclient_command(struct debconfclient *client,
const char *command, ...)
{
(brace on same line or next line). Also, do people want a space
before
Is there a particular coding style which people prefer?
I'd say it depends on the module you are working on. Just stay
consistent with the body of code you are working on.
randolph
--
Debian Developer [EMAIL PROTECTED]
http://www.TauSq.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
8 matches
Mail list logo
