mirror of
https://github.com/cpp-best-practices/cppbestpractices.git
synced 2025-12-17 03:04:36 +03:00
Update 03-Style.md
Make additional note about `t_` and `m_` suggested prefixes. Closes #11
This commit is contained in:
@@ -31,7 +31,7 @@ Name function parameters with an `t_` prefix. `t_` can be thought of as "the", b
|
|||||||
|
|
||||||
By using `t_` for parameters and `m_` for module data, we can have consistency with both public members of structs and private members of classes.
|
By using `t_` for parameters and `m_` for module data, we can have consistency with both public members of structs and private members of classes.
|
||||||
|
|
||||||
Any prefix or postfix can be chosen for your organization. This is just one example.
|
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).
|
||||||
|
|
||||||
```cpp
|
```cpp
|
||||||
struct Size
|
struct Size
|
||||||
|
|||||||
Reference in New Issue
Block a user