From 75e12df80854d1d7f2503acc211ddb8711a79ca9 Mon Sep 17 00:00:00 2001 From: Jason Turner Date: Wed, 25 May 2016 15:32:23 -0600 Subject: [PATCH] Update 03-Style.md --- 03-Style.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/03-Style.md b/03-Style.md index 9909e69..137889d 100644 --- a/03-Style.md +++ b/03-Style.md @@ -31,8 +31,6 @@ The most important thing is consistency within your codebase; this is one possib 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. -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. - 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