From: MARK CALLAGHAN Date: March 5 2009 4:39pm Subject: Re: MySQL University Session: Good Coding Style follow up List-Archive: http://lists.mysql.com/internals/36337 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Mar 5, 2009 at 8:25 AM, Ingo Str=FCwing wr= ote: > Hi, > > MARK CALLAGHAN, 05.03.2009 16:42: > > ... >> 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. > > > I concur. I'd rather stick to a common coding style (even if I hate it), > than to switch between different (possibly nice) styles when looking > into different code areas. > > Having someone to drive updates of the common style guideline is a good > idea. I also agree that the changes should be somewhat democratic > legitimated (e.g. by surveys). It isn't democratic for me and I contribute a lot: bug fixes, bug reports, tests and code changes. But I am willing to forgo that right if it makes a decision more likely. However, I think that allowing each area to have a separate style is a lack of a decision. --=20 Mark Callaghan mdcallag@stripped