RADProgrammer Style Guide Glossary

• Camel Case: A multiple word phrase in which each word begins with a capital letter withno intervening spaces or punctuation. (Typically requires the first word to be in lower case, camelCase)
• Closed-Form Compound Word: Words formed when two fully independant, unique words are combined to create a new word. (snowball, everything, endpoint, callback, mailbox)
• Code Smell: Indicator of a type of coding that is inherently prone to not-so-obvious problems and a better implementation may be needed. Examples could include a method with a lot of variables, a method with more than a full line's width of parameters, a class trying to accomplish too many different actions, and duplicated or nearly- identical code. New code smells can be learned over time by repeatedly fixing similar problems.
• Hyphenated Compound Word: Words formed when two separate words are joined together by a hyphen. (check-in, long-term, one-half)
• Identifier: Names of source code items such as constants, variables, fields, types, properties, methods, units, and packages.
• Open Compound Word: Words formed when two words remain separate but are used together to create a new idea with specific meaning. (no one, living room, post office)
• Pascal Case: A multiple word phrase in which each word begins with a capital letter with no intervening spaces or punctuation. (AKA: InfixCaps, upper camel case)
• Snake Case: A multiple word phrase in which all spaces are replaced with underscores (with all-upper and all-lower case versions.)
• Wiki Case: A more restrictive version of Pascal Case which does not allow one letter words. (ReadALine is not allowed but ReadOneLine is)