On Thu, Mar 5, 2009 at 7:11 AM, Konstantin Osipov <kostja@stripped> wrote:
> As a follow up to the MySQL University session on the coding
> style today, let me present a proposal for the process around it
> to your criticism.
> To those who missed the session: the main idea with the server
> coding style I advocate is that we need to revive it, make it a
> living document.
> The proposal below allows for flexibility within technical teams
> -- either to appoint a coding style captain, or vote on every
> change separately. A team can decide to share a coding style with
> another team.
> The main point is that the new process allows to introduce
> changes, and assigns out responsibilities, too.
> Coding style.
> All code contributed to the server must adhere to a coding
> style. Since many parts of the server historically originate from
> different development environments, it seems unnecessary to demand
> that all technical teams follow the same style. Besides, the
> existing code base doesn't satisfy this requirement.
Excluding storage engines, I hoped that MySQL would go from no
enforcement of coding style to enforcement for their chosen style. The
URL you cite describes a style. Why can't all code other than storage
engines accept that? If there is a coding style per area then those of
us who work on code in multiple areas need multiple vim/emacs config
files. Code styles are bound to generate a lot of process and
criticism. With one style rather than many, much less energy will be
used for all of that.
And to make this more fun, how are files in the sql directory
classified? And who are the captains? How many different guides must I
remember if I were to review a patch?
No role has been described for the external developer community.