Click here to Skip to main content
15,912,069 members

Survey Free Text Answers

Naming conventions in your code

24 Nov 2003 to 30 Nov 2003 What notations do you use when coding?

Text entry answers for sorted by frequency of occurrance.

(2) All of the above
(2) Mixture
(2) Simplified hungarian. s denotes string, char*, CString, etc. n denotes some numeric type. etc.
(2) _
(1) 1,3 and 4
(1) a lower case prefix for scope & Pascal Cased element name (e.g. cVariableName for a class instance variable)
(1) aaaa
(1) AddString
(1) small case names for local variables, hungarian for members and parameters (without underscores)
(1) STL style (number_of_days, is_valid)
(1) sutter
(1) Sutter's convention
(1) this_way
(1) Use both (Pascal for public properties & methods and Camel for internal,private and protected properties, fields and methods)
(1) Variables different from local variables, locals different from members, members different from globals
(1) VB style
(1) visual c++6.0
(1) web cam
(1) well... other.
(1) WM_UNICHAR
(1) Yes.
(1) Mixture of Camel and Pascal to denote differences in declaration
(1) mobile agent
(1) multimedia
(1) my and our; e.g. myDataPoint or ourStaticSetting
(1) My Own conventions is the better...
(1) myMemberVariable, aParameter, ourStaticVariable
(1) none
(1) None (The compiler handles types for me)
(1) Pascal Case with Prefixes
(1) Pascal for methods, Camel for variables
(1) Pascal, or whatever is the convention in that project.
(1) PascalCase (methods, properties, class names) - camelCase (method arguments) - lower_case_with_underscore (local method variables) - _camelCase with leading underscore (class fields)
(1) Pascal's Hungarian Camel (mix of all)
(1) Sam Blackburn's WFC naming convention
(1) ScreenSaver
(1) Several
(1) Simlpe notation that is easy to understand
(1) All of the above when appropriate
(1) All of them depending on the existing code
(1) All of them!
(1) aLtErNaTiNg CaSe
(1) and Camel
(1) Both Camel and Pascal
(1) Both Camel and Pascal as appropriate
(1) Both Pascal notation, Camel Caps
(1) button
(1) c/c++ standard notation with prefixes for globals (g_), statics (s_), members (m_)
(1) C/C++ standard way (e.g., number_of_days)
(1) Camel & Pascal case (MS.NET convention)
(1) Camel and Pascal
(1) Camel Caps and Hungarian notation with prefixes
(1) camel for variables and parameters, pascal for types and methods
(1) Camel for variables, Pascal for methods
(1) Camel for vars, Pascal for types / classes / functions.
(1) Camel w/prefixes for members, none for locals
(1) CamelCaps with prefix (a,p,k,g,C,T)
(1) CListCtrl
(1) COBOL case
(1) codebars
(1) Combination
(1) Combination of 1 and 4
(1) Combination of Camel and Pascal
(1) Combination of hungarian and camel caps.
(1) Combination of Hungarian w/ prefixes and Pascal case
(1) cursor
(1) Depends: for Java: camel; for C#: camel for variables, pascal for methods; C++: hungarian and camel
(1) Dutch notation with prefixes
(1) Follow the MS Guildlines for .NET as far as company policy allows.
(1) Huingarian without type info
(1) Hungarian casing (public=AllCaps, member=smallletters, method-level=m_MemberName), .NET datatype indicators ( DataTypeCollection, etc)
(1) Hungarian with Pascal Case
(1) hungarian, camel humps, and my own adapted convention
(1) Hungarian/Camel Caps Combo - CC user defined types, HN for system types
(1) I use hungarian for variable names and Pascal case for method and function names.
(1) It Depends
(1) Java games with source code
(1) K&R
(1) l33t notation (1nUmB3r, m_1NuMb3r etc)
(1) lower case
(1) lower case seperated by underscore ( m_first_name )
(1) m_ but no Hungarian !
(1) Meaningful names, underscore delimited, and trailing underscores for class private data members.
(1) mine
(1) mix (Pascal case for public methods and properties, underscores as in number_of_days for variables)
(1) mix of these
(1) Mixed, parameters Pascal, private data members Hungarian, local method Camel
(1) mix'n'match