I just wanted to kindly ask why you don't use the name conventions given by ymir or just any convention for yourself. Is there any reason to call the variable m_EnterToken instead of m_bEnterToken for example? Or naming the vector multi_line instead of m_vecMultiLine?
They're called hungarian notation (1972–1981), here you can find everything about it.
Bitte melden Sie sich an, um diesen Link zu sehen.
Bitte melden Sie sich an, um diesen Link zu sehen.
No I don't recommend 'Hungarian'. I regard 'Hungarian' (embedding an abbreviated version of a type in a variable name) as a technique that can be useful in untyped languages, but is completely unsuitable for a language that supports generic programming and object-oriented programming — both of which emphasize selection of operations based on the type and arguments (known to the language or to the run-time support). In this case, 'building the type of an object into names' simply complicates and minimizes abstraction.
Bitte melden Sie sich an, um diesen Link zu sehen.
Encoding the type of a function into the name (so-called Hungarian notation) is brain damaged—the compiler knows the types anyway and can check those, and it only confuses the programmer.
Bitte melden Sie sich an, um diesen Link zu sehen.
... nowadays HN and other forms of type encoding are simply impediments. They make it harder to change the name or type of a variable, function, member or class. They make it harder to read the code. And they create the possibility that the encoding system will mislead the reader.
Bitte melden Sie sich an, um diesen Link zu sehen.
Design Guidelines[14] discourage developers from using Systems Hungarian notation when they choose names for the elements in .NET class libraries, although it was common on prior Microsoft development platforms like Visual Basic 6 and earlier. These Design Guidelines are silent on the naming conventions for local variables inside functions.