While in the general case it is more a question of style, there are subtle differences, if you have member attributes with more than one access level, in:
- initialization order of members
- (potentially) memory layout of the object
The order of initialization of members in the constructor initialization list is the same order in which the attributes appear in the class definition, so if you place public attributes before private attributes all public attributes will be initialized before any private attribute (this will really affect code only if you use some attribute as an argument to the constructor of a different attribute).
Potentially, the memory layout of the object may differ. All fields with the same access level are lay out in memory in the same order in which they are declared in the class. The compiler is free to reorder different access levels as it wish (i.e. lay out in memory public before protected before private...) but many don't. The memory layout of the object will be different if you reorder the access levels and there are fields in more than one access level --unless the compiler reorders member attributes.