Skip to content

Commit 75e12df

Browse files
committedMay 25, 2016
Update 03-Style.md
1 parent 251eb8f commit 75e12df

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed
 

‎03-Style.md

-2
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,6 @@ The most important thing is consistency within your codebase; this is one possib
3131

3232
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.
3333

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-
3634
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).*
3735

3836
```cpp

0 commit comments

Comments
 (0)