On Fri, Mar 6, 2009 at 12:02 PM, Konstantin Osipov <kostja@stripped> wrote:
> * Michael Widenius <monty@stripped> [09/03/06 19:22]:
>> Konstantin> I agree. How would you, however, enforce a single style in a
>> Konstantin> distributed organization without a single leader, like ours?
>> I am still working on the MySQL code base and at least I will enforce
>> the current coding style on the MySQL-Maria distribution.
>> I don't see
>> why the MySQL group at Sun should not be able to do the same on their
>> code base.
> Because not everybody agrees with the current coding style,
> and some roles and responsibilities are now missing.
>> Konstantin> In the proposal, I suggest that a single module always follows a
>> Konstantin> single style. sql/ is mainly runtime and the optimizer. I
>> Konstantin> certainly hope that we will be able to follow a single style.
>> Having different coding styles per team is not something that would
>> work in the long term; This is especially confusing when team moves to
>> do different things in other parts of the server. It's also hard for
>> anyone who wants to contribute code to the MySQL project.
> I agree. It seems that all server tech leads also accept that we
> need a single style now, especially after this thread.
That is great news. I doubt that any style will be loved by all, but
that is much better than N styles that are disliked by most.