Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | Lars Gullik Bjønnes wrote:
| > | > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > | > | | Do you mean this one:
| > | > | | > - Long variables are named like thisLongVariableName.
| > | > | | So without the trailing underscore then?
| > | > No. Private class member variables get a _ at the end.
| > | | Where is that written? And what about protected member?
| > No _.
|
| Too bad... How do you handle the case where you need an access method
| then? This won't work:
|
| public:
| OneType oneType() { return oneType; }
|
| protected:
| OneType oneType;
|
| I think we need the trailing underscore for protected members. Another
| solution is to ban protected members.
yes. that would be nice.
| > | So you see it's difficult to extract a clear figure from this code and
| > | I would say that the "one_type_" style is used quite often...
| > Yes, we have gotten confused by boost and stl/std.
|
| So I reckon you want to stick with:
| - "oneMethod()" style for member methods.
| - "oneType_" for private member variable
| - "oneType" style for protected member variable. This one need more
| discussion.
right.
--
Lgb
