Brian Aker wrote: > Hi! > > I can go either way with this, but I know that in some cases we need > to have it mixed. > > There is also the issue of creating "holes" in the structure. When > packing the structures/classes we can't always be neat about this.
Totally agree with that! Perhaps suggest then: public: protected: private: methods... then all member variables starting off in that order (which should be fine, because they should all be private anyway) but with exceptions as needed for packing reasons? > Cheers, -Brian > > On Feb 8, 2010, at 8:55 AM, 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. >> >> Thanks, Padraig >> >> _______________________________________________ Mailing list: >> https://launchpad.net/~drizzle-discuss Post to : >> [email protected] Unsubscribe : >> https://launchpad.net/~drizzle-discuss More help : >> https://help.launchpad.net/ListHelp > > > _______________________________________________ Mailing list: > https://launchpad.net/~drizzle-discuss Post to : > [email protected] Unsubscribe : > https://launchpad.net/~drizzle-discuss More help : > https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
