Padraig O'Sullivan wrote: > Hi! > > I was working on a class today in Drizzle and wasn't sure what the > coding standard is with regard to declaration order i.e. public before > private or private before public. There is a sub-section on this in > the coding standards right now which indicates no conclusion was made: > > http://drizzle.org/wiki/Coding_Standards#Declaration_Order > > Personally, I prefer public before private. But I'd like to at least > choose one order and place it in the coding standards so we can be > consistent.
Both the Google C++ coding standards [1] and the Ellemtel C++ standards [2] require public: then protected: then private:. [3][4] I tend to agree... when I start reading a class def, I'm usually looking for API first, and I can read further if I want to see implementation details. So my vote is to swipe the text from the Google standard (I like their supplementary text too. [1] http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml [2] http://www.doc.ic.ac.uk/lab/cplus/c++.rules/ [3] http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Declaration_Order [4] http://www.doc.ic.ac.uk/lab/cplus/c++.rules/chap6.html#sect1 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
