Snake case (stylized as snake_case) refers to the style of writing in which each space is replaced by an underscore (_) character, and the first letter of each word written in lowercase. It is a commonly used naming convention in computing, for example for variable and subroutine names, and for filenames. One study has found that readers can recognize snake case values more quickly than camel case.
The use of underscores as word separators dates back to the late 1960s. It is particularly associated with C, being found in The C Programming Language (1978), and contrasted with pascal case (a type of camel case). However, the convention traditionally had no specific name: the Python programming language style guide refers to it simply as "lower_case_with_underscores".
"BTW...what *do* you call that naming style? snake_case? That's what I'll call it until someone corrects me."
However, former Intel engineer Jack Dahlgren has stated that he was using the term internally at Intel (and perhaps in dialogue with Microsoft engineers) in 2002.[failed verification] It is possible that the term developed independently in more than one community.
As of 2015[update], names for other delimiter-separated naming conventions for multiple-word identifiers have not been standardized, although some terms have increasing levels of usage, such as lisp-case, kebab-case, SCREAMING_SNAKE_CASE, and more.
A list of programming languages which conventionally use snake case
- C++, Boost
- C, for some type names in the standard library, but not for function names.
- Eiffel, for class and feature names
- Elixir, for atom, variable, and function names
- Erlang, for function names
- GDScript, for variable and function names
- Java, for static final constants and enum values.
- OCaml, for value, type, and module names
- Perl, for lexical variables and subroutines
- Oracle SQL and PL/SQL, for all unquoted identifiers (tables, columns, indexes, constraints, PL/SQL variables, constants, procedures/functions, triggers,...), although not official by Oracle itself, still recommended by majority of known "influencers" and used throughout the official Oracle documentation
- All unquoted snake_case identifiers are actually internally represented as SCREAMING_SNAKE_CASE identifiers.
- Prolog, for both atoms (predicate names, function names and constants) and variables
- Python, for variable names, function names, method names, and module or package (i.e. file) names
- PHP uses SCREAMING_SNAKE_CASE for class constants
- R, for variable names, function names, argument names, especially in the tidyverse style
- Ruby, for variable and method names
- Rust, for variable names, function names, method names, module names and macros
- Camel case, more common in Java and C#
- Kebab case, more common in LISP
- Naming convention (programming)
- Sharif, Bonita; Maletic, Jonathan I. (2010). "An Eye Tracking Study on camelCase and under_score Identifier Styles". 2010 IEEE 18th International Conference on Program Comprehension (PDF). pp. 196–205. CiteSeerX 10.1.1.421.6137. doi:10.1109/ICPC.2010.41. ISBN 978-1-4244-7604-6. S2CID 14170019.
- Guido van Rossum, Barry Warsaw, Nick Coghlan (2001-07-05). "PEP 0008 -- Style Guide for Python Code".CS1 maint: uses authors parameter (link)
- Gavin Kistner (2004-02-23). "Appropriate use of camelCase". Newsgroup: comp.lang.ruby. Usenet: [email protected]_s02. Retrieved 2015-08-13.
- "Quora". 2013-05-10.
- "StackOverflow - What's the name for snake_case with dashes?".
- "Programmers - If this is camelCase what-is-this?".
- "Camel_SNAKE-kebab". 23 April 2020.
- "Naming Conventions in ABAP Objects". help.sap.com. Retrieved 2020-07-28.
- "Boost Library Requirements and Guidelines". Retrieved 2015-08-13.
- "Eiffel Class and Feature Names". 28 December 2019.
- "Elixir Style Guide". May 2020.
- "Programming Rules". Retrieved 2017-08-11.
- "GDScript Style Guide".
- "Xen wiki". Retrieved 2017-03-15.
- Damian Conway (2005). Perl Best Practices. O'Reilly Media Inc. p. 44. ISBN 978-0596001735.
- "Quick Guide to Some Sources for Naming Conventions for Oracle Database Development". stevenfeuersteinonplsql.blogspot.com. Retrieved 2020-12-30.
- Michael A. Covington; Roberto Bagnara; Richard A. O'Keefe; Jan Wielemaker; Simon Price (2009). "Coding Guidelines for Prolog (v.3)". p. 14. arXiv:0911.2899 [cs.PL].
- Wickham, Hadley. The tidyverse style guide.
- "Ruby Naming Conventions". May 2020.
- "Naming - Rust API Guidelines".