You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 03-Style.md
-2
Original file line number
Diff line number
Diff line change
@@ -31,8 +31,6 @@ The most important thing is consistency within your codebase; this is one possib
31
31
32
32
Name function parameters with an `t_` prefix. `t_` can be thought of as "the", but the meaning is arbitrary. The point is to distinguish function parameters from other variables in scope while giving us a consistent naming strategy.
33
33
34
-
By using `t_` for parameters and `m_` for member data, we can have consistency with both public members of structs and private members of classes.
35
-
36
34
Any prefix or postfix can be chosen for your organization. This is just one example. *This suggestion is controversial, for a discussion about it see issue [#11](https://github.com/lefticus/cppbestpractices/issues/11).*
0 commit comments