Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Camel case
open-in-new
<h2 id="variations-and-synonyms">Variations and synonyms</h2> <p>The practice has various names, including: </p> <ul><li>camelBack (or camel-back) notation<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> or CamelCaps<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a></li> <li>camel case or CamelCase</li> <li>CapitalizedWords or CapWords for upper camel case in <a href="/facts/Python_(programming_language)/YbuGqofa">Python</a><a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a></li> <li>compoundNames<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a></li> <li>Embedded caps (or embedded capitals)<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a></li> <li>HumpBack (or hump-back) notation<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a></li> <li>InterCaps or intercapping<a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a> (abbreviation of <i>Internal Capitalization</i><a class="footnote-ref" id="fnref:16" href="#fn:16"><sup>16</sup></a>)</li> <li>medial capitals, recommended by the <a href="/facts/Oxford_English_Dictionary/qaxKX8Bc">Oxford English Dictionary</a><a class="footnote-ref" id="fnref:17" href="#fn:17"><sup>17</sup></a></li> <li>mixedCase for lower camel case in Python<a class="footnote-ref" id="fnref:18" href="#fn:18"><sup>18</sup></a></li> <li>PascalCase for upper camel case<a class="footnote-ref" id="fnref:19" href="#fn:19"><sup>19</sup></a><a class="footnote-ref" id="fnref:20" href="#fn:20"><sup>20</sup></a><a class="footnote-ref" id="fnref:21" href="#fn:21"><sup>21</sup></a> (after the <a href="/facts/Pascal_(programming_language)/b3yvp8bF">Pascal programming language</a>)</li> <li><a href="/facts/Smalltalk/Ru2UPVDE">Smalltalk</a> case</li> <li>WikiWord<a class="footnote-ref" id="fnref:22" href="#fn:22"><sup>22</sup></a> or WikiCase<a class="footnote-ref" id="fnref:23" href="#fn:23"><sup>23</sup></a> (especially in older <a href="/facts/Wiki/uCKCEzqb">wikis</a>)</li></ul> <h2 id="history">History</h2> <p>The earliest known occurrence of the term "InterCaps" on Usenet is in an April 1990 post to the group alt.folklore.computers by Avi Rappoport.<a class="footnote-ref" id="fnref:24" href="#fn:24"><sup>24</sup></a> The earliest use of the name "Camel Case" occurs in 1995, in a post by Newton Love.<a class="footnote-ref" id="fnref:25" href="#fn:25"><sup>25</sup></a> Love has since said, "With the advent of programming languages having these sorts of constructs, the humpiness of the style made me call it HumpyCase at first, before I settled on CamelCase. I had been calling it CamelCase for years. ... The citation above was just the first time I had used the name on USENET."<a class="footnote-ref" id="fnref:26" href="#fn:26"><sup>26</sup></a> The term "Pascal Case" was coined in design discussions for the <a href="/facts/.NET_Framework/J6QDAUhP">.NET Framework</a>, first released in 2002.<a class="footnote-ref" id="fnref:27" href="#fn:27"><sup>27</sup></a> </p> <h2 id="traditional-use-in-natural-language">Traditional use in natural language</h2> <h3>In word combinations</h3> <p>The use of medial capitals as a convention in the regular spelling of everyday texts is rare, but is used in some languages as a solution to particular problems which arise when two words or segments are combined. </p><p>In Italian, pronouns can be suffixed to verbs, and because the honorific form of second-person pronouns is capitalized, this can produce a sentence like <i>non ho trovato il tempo di risponderLe</i> ("I have not found time to answer you" – where <i>Le</i> means "to you"). </p><p>In German, many nouns denoting people lack a gender-neutral form, which is why often, especially colloquially, the male form of a noun is used generically to address everyone, regardless of their gender (this is called <i><a href="/facts/Gender_neutrality_in_languages_with_gendered_third-person_pronouns/4Ale4XS2">generisches Maskulinum</a></i> in German). Another, more recent approach is using the medial capital letter <a href="/facts/I/2w7mqI7e">I</a>, called <i><a href="/facts/Binnen-I/y5KWuShb">Binnen-I</a></i>, in written text for words like <i>StudentInnen</i> ("students") to indicate that both <i>Studenten</i> ("male students") and <i>Studentinnen</i> ("female students") are referred to simultaneously. However, mid-word capitalization does not conform to the <a href="/facts/German_orthography/wRfTdcfG">German orthography</a> prescribed by the <i><a href="/facts/Rat_f%25C3%25BCr_deutsche_Rechtschreibung/GKJnebP8">Rat für deutsche Rechtschreibung</a></i> (Council for German Orthography) apart from proper names like <i>McDonald</i>. In order to adhere to orthography, the introductory “students” example could be corrected using <a href="/facts/Parentheses/yzGM9J8A">parentheses</a> to <i>Student(inn)en</i>, which is analogous to writing "congress(wo)men" in English.<a class="footnote-ref" id="fnref:28" href="#fn:28"><sup>28</sup></a> </p><p>In <a href="/facts/Irish_orthography/tk5sPGW3">Irish</a>, camel case is used when an inflectional prefix is attached to a proper noun, for example <i>i nGaillimh</i> ("in <a href="/facts/Galway/7fJ5vqJW">Galway</a>"), from <i>Gaillimh</i> ("Galway"); <i>an tAlbanach</i> ("the Scottish person"), from <i>Albanach</i> ("Scottish person"); and <i>go hÉirinn</i> ("to Ireland"), from <i>Éire</i> ("Ireland"). In recent <a href="/facts/Scottish_Gaelic_orthography/5ar8xEwY">Scottish Gaelic orthography</a>, a hyphen has been inserted: <i>an t-Albannach</i>. </p><p>This convention of inflectional prefix is also used by several written <a href="/facts/Bantu_languages/6xKvpQ1a">Bantu languages</a> (e.g. <i>isiZulu</i>, "<a href="/facts/Zulu_language/qzd3p6Yr">Zulu language</a>") and several indigenous <a href="/facts/Languages_of_Mexico/vR6TSXCf">languages of Mexico</a> (e.g. <a href="/facts/Nahuatl_languages/e0Az8SMf">Nahuatl</a>, <a href="/facts/Totonacan_languages/tb3ADpov">Totonacan</a>, <a href="/facts/Mixe%25E2%2580%2593Zoque_languages/WouQV2tK">Mixe–Zoque</a>, and some <a href="/facts/Oto-Manguean_languages/6GfAjgxG">Oto-Manguean languages</a>). </p><p>In <a href="/facts/Dutch_language/yIB5lbsx">Dutch</a>, when capitalizing the digraph <i><a href="/facts/IJ_(digraph)/8B1kKF8Q">ij</a></i>, both the letter <i>I</i> and the letter <i>J</i> are capitalized, for example in the country name <i><a href="/facts/Iceland/E4KGYs2j">IJsland</a></i> ("Iceland"). </p><p>In <a href="/facts/Mandarin_Chinese/yxvDg67C">Chinese</a> <a href="/facts/Pinyin/pUwjfMXg">pinyin</a>, camel case is sometimes used for place names so that readers can more easily pick out the different parts of the name. For example, places like Beijing (北京), Qinhuangdao (秦皇岛), and Daxing'anling (大兴安岭) can be written as <i>BeiJing</i>, <i>QinHuangDao,</i> and <i>DaXingAnLing</i> respectively<i>,</i> with the number of capital letters equaling the number of <a href="/facts/Chinese_characters/5pn1PFvj">Chinese characters</a>. Writing word compounds only by the initial letter of each character is also acceptable in some cases, so Beijing can be written as <i>BJ</i>, Qinghuangdao as <i>QHD,</i> and Daxing'anling as DXAL. </p><p>In English, medial capitals are usually only found in Scottish or Irish "Mac-" or "Mc-" patronymic names, where for example <i>MacDonald, McDonald,</i> and <i>Macdonald</i> are common spelling variants of <a href="/facts/MacDonald_(surname)/zmVtcmsU">MacDonald</a> (son of Dòmhnall), and in Anglo-Norman "Fitz-" names, where for example both <i><a href="/facts/FitzGerald_(surname)/CUDzQhd9">FitzGerald</a></i> and <i>Fitzgerald</i> (son of Gerald) are found. </p><p>In their English style guide <i><a href="/facts/The_King%2527s_English/E6Dnvkes">The King's English</a></i>, first published in 1906, <a href="/facts/Henry_Watson_Fowler/D2ge7NbG">H. W.</a> and <a href="/facts/Francis_George_Fowler/n9YYj0z8">F. G. Fowler</a> suggested that medial capitals could be used in triple <a href="/facts/Compound_word/IbumXJgd">compound words</a> where <a href="/facts/Hyphen/2qtCxIGv">hyphens</a> would cause ambiguity—the examples they give are <i>KingMark-like</i> (as against <i>King Mark-like</i>) and <i>Anglo-SouthAmerican</i> (as against <i>Anglo-South American</i>). However, they described the system as "too hopelessly contrary to use at present".<a class="footnote-ref" id="fnref:29" href="#fn:29"><sup>29</sup></a> </p><p>Some French names also uses CamelCase names, such as <a href="/facts/LeBeau_(surname)/bw3oSqlH">LeBeau (surname)</a>, <a href="/facts/LaRue/rpPkqoLE">LaRue</a>, <a href="/facts/DeMordaunt/6pwjgUHc">DeMordaunt</a>, and Italian names <a href="/facts/DeRose/Sx9653Vv">DeRose</a>/<a href="/facts/Rosa_(surname)/Cy0tuvev">DeRosa</a>. </p> <h3>In transliterations</h3> <p>In the scholarly transliteration of languages written in other scripts, medial capitals are used in similar situations. For example, in transliterated <a href="/facts/Hebrew_language/hqKCSy9d">Hebrew</a>, <i>haIvri</i> means "the Hebrew person" or "the Jew" and <i>b'Yerushalayim</i> means "in Jerusalem". In <a href="/facts/Standard_Tibetan/SVRgs3bM">Tibetan</a> proper names like <i>rLobsang</i>, the "r" stands for a prefix glyph in the original script that functions as <a href="/facts/Tone_(linguistics)/eprhXrWJ">tone</a> marker rather than a normal letter. Another example is <i>tsIurku</i>, a Latin transcription of the <a href="/facts/Chechen_language/mCR0dGnY">Chechen</a> term for the capping stone of the characteristic <a href="/facts/Vainakh_medieval_towers/Lwud2k8l">Medieval defensive towers</a> of <a href="/facts/Chechnya/mjpuy4nm">Chechnya</a> and <a href="/facts/Ingushetia/pEDo7uYn">Ingushetia</a>; the letter "I" (<a href="/facts/Palochka/4oIT16Eh">palochka</a>) is not actually capital, denoting a <a href="/facts/Phoneme/EXGHlJ7a">phoneme</a> distinct from the one transcribed as "i". </p> <h3>In abbreviations</h3> <p>Medial capitals are traditionally used in abbreviations to reflect the capitalization that the words would have when written out in full, for example in the academic titles PhD or <a href="/facts/Bachelor_of_Science/9n3gvDf7">BSc</a>. A more recent example is <a href="/facts/NaNoWriMo/u5HsxUCD">NaNoWriMo</a>, a contraction of National Novel Writing Month and the designation for both the annual event and the nonprofit organization that runs it. In German, the names of statutes are abbreviated using embedded capitals, e.g. StGB for <i><a href="/facts/Strafgesetzbuch/rDsmnMal">Strafgesetzbuch</a></i> (Criminal Code), PatG for <i>Patentgesetz</i> (Patent Act), BVerfG for <i>Bundesverfassungsgericht</i> (<a href="/facts/Federal_Constitutional_Court/fdDeByo9">Federal Constitutional Court</a>), or the very common GmbH, for <i><a href="/facts/Gesellschaft_mit_beschr%25C3%25A4nkter_Haftung/yr4nvjrH">Gesellschaft mit beschränkter Haftung</a></i> (<a href="/facts/Private_limited_company/ax0as47z">private limited company</a>). In this context, there can even be three or more camel case capitals, e.g. in TzBfG for <i>Teilzeit- und Befristungsgesetz</i> (Act on Part-Time and Limited Term Occupations). In French, camel case acronyms such as <a href="/facts/Oulipo/FDPXrrey">OuLiPo</a> (1960) were favored for a time as alternatives to initialisms. </p><p>Camel case is often used to transliterate initialisms into alphabets where two letters may be required to represent a single character of the original alphabet, e.g., <a href="/facts/DShK/xmywlpsw">DShK</a> from <a href="/facts/Cyrillic/0btN3oWC">Cyrillic</a> ДШК. </p> <h2 id="history-of-modern-technical-use">History of modern technical use</h2> <h3>Chemical formulas</h3> <p>The first systematic and widespread use of medial capitals for technical purposes was the notation for chemical formulas invented by the Swedish chemist <a href="/facts/J%25C3%25B6ns_Jakob_Berzelius/HakSv3sP">Jacob Berzelius</a> in 1813. To replace the multitude of naming and symbol conventions used by chemists until that time, he proposed to indicate each chemical element by a symbol of one or two letters, the first one being capitalized. The capitalization allowed formulas like "<a href="/facts/Sodium_chloride/MWcXl3Mb">NaCl</a>" to be written without spaces and still be parsed without ambiguity.<a class="footnote-ref" id="fnref:30" href="#fn:30"><sup>30</sup></a><a class="footnote-ref" id="fnref:31" href="#fn:31"><sup>31</sup></a> </p><p>Berzelius' system continues to be used, augmented with three-letter symbols such as "<a href="/facts/Ununennium/WnpMG7CP">Uue</a>" for unconfirmed or unknown elements and abbreviations for some common substituents (especially in the field of organic chemistry, for instance "<a href="/facts/Ethyl_group/ydVhnBwD">Et</a>" for "ethyl-"). This has been further extended to describe the <a href="/facts/Amino_acid/WDxYwBny">amino acid</a> sequences of <a href="/facts/Protein/Jxmagu3E">proteins</a> and other similar domains. </p> <h3>Early use in trademarks</h3> <p>Since the early 20th century, medial capitals have occasionally been used for <a href="/facts/Corporation/hykSVoWJ">corporate</a> names and product trademarks, such as </p> <ul><li>DryIce Corporation (1925) marketed the solid form of <a href="/facts/Carbon_dioxide/xGzpppEp">carbon dioxide</a> (CO2) as "Dry Ice", thus leading to its common name.<a class="footnote-ref" id="fnref:32" href="#fn:32"><sup>32</sup></a></li> <li><a href="/facts/CinemaScope/2tIqWPnu">CinemaScope</a> and <a href="/facts/VistaVision/W1V74zFE">VistaVision</a>, rival <a href="/facts/Widescreen/SpJ8gcnV">widescreen</a> movie formats (1953)</li> <li><a href="/facts/ShopKo_Stores_Inc./JFK0c38f">ShopKo</a> (1962), retail stores, later renamed Shopko</li> <li><i>MisteRogers Neighborhood</i>, the TV series also called <i><a href="/facts/Mister_Rogers%2527_Neighborhood/dplvczMy">Mister Rogers' Neighborhood</a></i> (1968)<a class="footnote-ref" id="fnref:33" href="#fn:33"><sup>33</sup></a></li> <li>ChemGrass (1965), later renamed <a href="/facts/AstroTurf/Xr4ARzl8">AstroTurf</a> (1967)</li> <li><a href="/facts/ConAgra_Foods_Inc./DtULNMAD">ConAgra</a> (1971), formerly Consolidated Mills</li> <li><a href="/facts/MasterCraft/brP8pcwP">MasterCraft</a> (1968), a sports boat manufacturer</li> <li><a href="/facts/AeroVironment/WvAy2kaR">AeroVironment</a> (1971)</li> <li><a href="/facts/PolyGram/Sue5Vv2s">PolyGram</a> (1972), formerly Grammophon-Philips Group</li> <li><a href="/facts/UnitedHealth_Group/Fdyxrw5J">United HealthCare</a> (1977)<a class="footnote-ref" id="fnref:34" href="#fn:34"><sup>34</sup></a></li> <li><a href="/facts/MasterCard/M0lofWzy">MasterCard</a> (1979), formerly Master Charge</li> <li><a href="/facts/SportsCenter/S2fsqv7m">SportsCenter</a> (1979)</li></ul> <h3>Computer programming</h3> <p>In the 1970s and 1980s, medial capitals were adopted as a standard or alternative <a href="/facts/Naming_convention_(programming)/4IVCWpSU">naming convention</a> for multi-word <a href="/facts/Identifier_(computer_programming)/mBLrnPkj">identifiers</a> in several <a href="/facts/Programming_language/cWTYbgWa">programming languages</a>. The precise origin of the convention in computer programming has not yet been settled. A 1954 conference proceedings<a class="footnote-ref" id="fnref:35" href="#fn:35"><sup>35</sup></a> occasionally informally referred to <a href="/facts/IBM/QszA7nwd">IBM</a>'s <a href="/facts/Speedcoding/9ajmN8Cg">Speedcoding</a> system as "SpeedCo". <a href="/facts/Christopher_Strachey/hx9ToYVY">Christopher Strachey</a>'s paper on <a href="/facts/General_purpose_macro_processor/fFKXWVUT">GPM</a> (1965),<a class="footnote-ref" id="fnref:36" href="#fn:36"><sup>36</sup></a> shows a program that includes some medial capital identifiers, including "NextCh" and "WriteSymbol" (This was most likely the influence of the <a href="/facts/CPL_(programming_language)/WdCSdedV">CPL</a> language, of which Strachey was one of the designers) </p><p>Multiple-word descriptive identifiers with embedded spaces such as end of file or char table cannot be used in most programming languages because the spaces between the words would be <a href="/facts/Parser/nRKB01S3">parsed</a> as <a href="/facts/Delimiter/wRAQxIKV">delimiters</a> between <a href="/facts/Lexical_analysis/T1JYWpIf">tokens</a>. The alternative of running the words together as in endoffile or chartable is difficult to understand and possibly misleading; for example, chartable is an English word (able to be charted), whereas charTable means a table of chars . </p><p>Some early programming languages, notably <a href="/facts/Lisp_(programming_language)/xJHA3CrX">Lisp</a> (1958) and <a href="/facts/COBOL/wVnhqs0k">COBOL</a> (1959), addressed this problem by allowing a <a href="/facts/Hyphen/2qtCxIGv">hyphen</a> ("-") to be used between words of compound identifiers, as in "END-OF-FILE": Lisp because it worked well with prefix notation (a Lisp parser would not treat a hyphen in the middle of a symbol as a subtraction operator) and COBOL because its operators were individual English words. This convention remains in use in these languages, and is also common in program names entered on a <a href="/facts/Command_line/R9JpGmXQ">command line</a>, as in Unix. </p><p>However, this solution was not adequate for mathematically oriented languages such as <a href="/facts/FORTRAN/m1KqjcMU">FORTRAN</a> (1955) and <a href="/facts/ALGOL_58/CbHqs9GR">ALGOL</a> (1958), which used the hyphen as an infix subtraction operator. FORTRAN ignored blanks altogether, so programmers could use embedded spaces in variable names. However, this feature was not very useful since the early versions of the language restricted identifiers to no more than six characters. </p><p>Exacerbating the problem, common <a href="/facts/Punched_card/44WsPulQ">punched card</a> character sets of the time were uppercase only and lacked other special characters. It was only in the late 1960s that the widespread adoption of the <a href="/facts/ASCII/vGUI33Qu">ASCII</a> character set made both lowercase and the <a href="/facts/Underscore/KJsRo3tA">underscore</a> character _ universally available. Some languages, notably <a href="/facts/C_(programming_language)/Ky2No763">C</a>, promptly adopted underscores as word separators, and identifiers such as end_of_file are still prevalent in C programs and libraries (as well as in later languages influenced by C, such as <a href="/facts/Perl/fx31kjlT">Perl</a> and <a href="/facts/Python_(programming_language)/YbuGqofa">Python</a>). However, some languages and programmers chose to avoid underscores and adopted camel case instead. </p><p><a href="/facts/Charles_Simonyi/AnWGomNN">Charles Simonyi</a>, who worked at <a href="/facts/Xerox_PARC/fh2Su0k9">Xerox PARC</a> in the 1970s and later oversaw the creation of Microsoft's Office suite of applications, invented and taught the use of <a href="/facts/Hungarian_Notation/m4kfpJ5u">Hungarian Notation</a>, one version of which uses the lowercase letter(s) at the start of a (capitalized) variable name to denote its type. One account claims that the camel case style first became popular at Xerox PARC around 1978, with the <a href="/facts/Mesa_(programming_language)/etxwQkV5">Mesa programming language</a> developed for the <a href="/facts/Xerox_Alto/6pjFTD0A">Xerox Alto</a> computer. This machine lacked an underscore key (whose place was taken by a left arrow "←"), and the hyphen and space characters were not permitted in identifiers, leaving camel case as the only viable scheme for readable multiword names. The PARC Mesa Language Manual (1979) included a coding standard with specific rules for upper and lower camel case that was strictly followed by the Mesa libraries and the Alto operating system. <a href="/facts/Niklaus_Wirth/krsLUB11">Niklaus Wirth</a>, the inventor of <a href="/facts/Pascal_(programming_language)/b3yvp8bF">Pascal</a>, came to appreciate camel case during a sabbatical at PARC and used it in <a href="/facts/Modula/pxLbgVF5">Modula</a>, his next programming language.<a class="footnote-ref" id="fnref:37" href="#fn:37"><sup>37</sup></a> </p><p>The <a href="/facts/Smalltalk/Ru2UPVDE">Smalltalk</a> language, which was developed originally on the Alto, also uses camel case instead of underscores. This language became quite popular in the early 1980s, and thus may also have been instrumental in spreading the style outside PARC. </p><p>Upper camel case (or "Pascal case") is used in <a href="/facts/Wolfram_Language/MDxl50Yq">Wolfram Language</a> in computer algebraic system <a href="/facts/Mathematica/dRwoGFG2">Mathematica</a> for predefined identifiers. User defined identifiers should start with a lower case letter. This avoids the conflict between predefined and user defined identifiers both today and in all future versions. </p><p>C# variable names are recommended to follow the lower camel case convention.<a class="footnote-ref" id="fnref:38" href="#fn:38"><sup>38</sup></a> </p> <h3>Computer companies and products</h3> <p>Whatever its origins in the computing field, the convention was used in the names of computer companies and their commercial brands, since the late 1970s — a trend that continues to this day: </p> <ul><li>(1977) <a href="/facts/CompuServe/Pjpdcf2a">CompuServe</a></li> <li>(1978) <a href="/facts/WordStar/QWnaF7t7">WordStar</a></li> <li>(1979) <a href="/facts/VisiCalc/6xnHrMKp">VisiCalc</a></li> <li>(1982) <a href="/facts/MicroProse/PfVMUsIV">MicroProse</a>, <a href="/facts/WordPerfect/x0R6HU9f">WordPerfect</a></li> <li>(1983) <a href="/facts/Novell_NetWare/cfnyxMzs">NetWare</a></li> <li>(1984) <a href="/facts/LaserJet/6yJzMrLR">LaserJet</a>, <a href="/facts/MacWorks/JUAEkYKQ">MacWorks</a>, <a href="/facts/PostScript/h2XwbcmC">PostScript</a></li> <li>(1985) <a href="/facts/Adobe_PageMaker/Lh9mcgzN">PageMaker</a></li> <li>(1987) <a href="/facts/ClarisWorks/0Jl8444t">ClarisWorks</a>, <a href="/facts/HyperCard/v9GQF9K2">HyperCard</a>, <a href="/facts/PowerPoint/putuX423">PowerPoint</a></li> <li>(1990) <a href="/facts/WorldWideWeb/FlgLKla7">WorldWideWeb</a> (the first web browser), later renamed Nexus</li></ul> <h3>Spread to mainstream usage</h3> <p>In the 1980s and 1990s, after the advent of the personal computer exposed hacker culture to the world, camel case then became fashionable for corporate <a href="/facts/Trade_name/0tbWP1Sn">trade names</a> in non-computer fields as well. Mainstream usage was well established by 1990: </p> <ul><li>(1980) <a href="/facts/EchoStar_Communications_Corporation/WGGXnqtP">EchoStar</a></li> <li>(1984) <a href="/facts/BellSouth/vT90BWJj">BellSouth</a></li> <li>(1985) <i><a href="/facts/EastEnders/z6g4tebu">EastEnders</a></i></li> <li>(1986) <i><a href="/facts/SpaceCamp/aFfPRLSS">SpaceCamp</a></i></li> <li>(1990) <a href="/facts/HarperCollins_Publishers/HHLz5lk5">HarperCollins</a>, <a href="/facts/SeaTac%2c_Washington/qBGjXMDx">SeaTac</a></li> <li>(1998) <a href="/facts/PricewaterhouseCoopers/4AuXcnh0">PricewaterhouseCoopers</a>, merger of Price Waterhouse and Coopers</li></ul> <p>During the <a href="/facts/Dot-com_bubble/dCFWQt0s">dot-com bubble</a> of the late 1990s, the lowercase prefixes "e" (for "<a href="/facts/Electronics/E4JhgISq">electronic</a>") and "i" (for "Internet",<a class="footnote-ref" id="fnref:39" href="#fn:39"><sup>39</sup></a> "information", "<a href="/facts/Intelligent/pRmAeRsw">intelligent</a>", etc.) became quite common, giving rise to names like <a href="/facts/Apple_Inc./oTJYta3k">Apple</a>'s <a href="/facts/IMac/Yx2fxTbD">iMac</a> and the <a href="/facts/Zentyal/X83QeA28">eBox</a> software platform. </p><p>In 1998, Dave Yost suggested that chemists use medial capitals to aid readability of long chemical names, e.g. write AmidoPhosphoRibosylTransferase instead of <a href="/facts/Amidophosphoribosyltransferase/CwstTrB9">amidophosphoribosyltransferase</a>.<a class="footnote-ref" id="fnref:40" href="#fn:40"><sup>40</sup></a> This usage was not widely adopted. </p><p>Camel case is sometimes used for abbreviated names of certain neighborhoods, e.g. New York City neighborhoods <i>SoHo</i> (<i>So</i>uth of <i>Ho</i>uston Street) and <i>TriBeCa</i> (<i>Tri</i>angle <i>Be</i>low <i>Ca</i>nal Street) and San Francisco's <i>SoMa</i> (<i>So</i>uth of <i>Ma</i>rket). Such usages erode quickly, so the neighborhoods are now typically rendered as <i>Soho</i>, <i>Tribeca</i>, and <i>Soma</i>. </p><p>Internal capitalization has also been used for other technical codes like <a href="/facts/HeLa/aP1fIhVX">HeLa</a> (1983). </p> <h2 id="current-usage-in-computing">Current usage in computing</h2> <h3>Programming and coding</h3> <p class="note">Main article: <a href="/facts/Naming_convention_(programming)/4IVCWpSU">Naming convention (programming)</a></p> <p>The use of medial caps for compound identifiers is recommended by the <a href="/facts/Coding_style/8HoSgA0e">coding style</a> guidelines of many organizations or software projects. For some languages (such as <a href="/facts/Mesa_(programming_language)/etxwQkV5">Mesa</a>, <a href="/facts/Pascal_(programming_language)/b3yvp8bF">Pascal</a>, <a href="/facts/Modula/pxLbgVF5">Modula</a>, <a href="/facts/Java_(programming_language)/9ScgFyAL">Java</a> and <a href="/facts/Microsoft/nGIDDXdx">Microsoft</a>'s <a href="/facts/.NET/PDMQdfFu">.NET</a>) this practice is recommended by the language developers or by authoritative manuals and has therefore become part of the language's "culture". </p><p>Style guidelines often distinguish between upper and lower camel case, typically specifying which variety should be used for specific kinds of entities: <a href="/facts/Variable_(computer_science)/VoCKtwml">variables</a>, <a href="/facts/Field_(computer_science)/jt622EDb">record fields</a>, <a href="/facts/Method_(computer_science)/8kAXxVYs">methods</a>, <a href="/facts/Procedure_(computer_science)/9vFJrg0A">procedures</a>, <a href="/facts/Function_(computer_science)/9vFJrg0A">functions</a>, <a href="/facts/Subroutine/9vFJrg0A">subroutines</a>, <a href="/facts/Type_(computer_science)/fcx5hgVL">types</a>, etc. These rules are sometimes supported by <a href="/facts/Static_code_analysis/b56nr6QM">static analysis</a> tools that check <a href="/facts/Source_code/o9J6Jv23">source code</a> for adherence. </p><p>The original <a href="/facts/Hungarian_notation/m4kfpJ5u">Hungarian notation</a> for programming, for example, specifies that a lowercase abbreviation for the "usage type" (not data type) should prefix all variable names, with the remainder of the name in upper camel case; as such it is a form of lower camel case. </p><p>Programming identifiers often need to contain <a href="/facts/Acronyms_and_initialisms/nlHK7aRt">acronyms and initialisms</a> that are already in uppercase, such as "old HTML file". By analogy with the title case rules, the natural camel case rendering would have the abbreviation all in uppercase, namely "oldHTMLFile". However, this approach is problematic when two acronyms occur together (e.g., "parse DBM XML" would become "parseDBMXML") or when the standard mandates lower camel case but the name begins with an abbreviation (e.g. "SQL server" would become "sQLServer"). For this reason, some programmers prefer to treat abbreviations as if they were words and write "oldHtmlFile", "parseDbmXml" or "sqlServer".<a class="footnote-ref" id="fnref:41" href="#fn:41"><sup>41</sup></a> However, this can make it harder to recognize that a given word is intended as an acronym.<a class="footnote-ref" id="fnref:42" href="#fn:42"><sup>42</sup></a> </p><p>Difficulties arise when identifiers have different meaning depending only on the case, as can occur with mathematical functions or trademarks. In this situation changing the case of an identifier might not be an option and an alternative name need be chosen. </p> <h3>Wiki link markup</h3> <p>Camel case is used in some <a href="/facts/Wikitext/uCKCEzqb">wiki markup languages</a> for terms that should be automatically linked to other <a href="/facts/Wiki/uCKCEzqb">wiki</a> pages. This convention was originally used in <a href="/facts/Ward_Cunningham/8SuK946v">Ward Cunningham</a>'s original <a href="/facts/Wiki_software/zNRxq6GV">wiki software</a>, <a href="/facts/WikiWikiWeb/K13WVqo1">WikiWikiWeb</a>,<a class="footnote-ref" id="fnref:43" href="#fn:43"><sup>43</sup></a> and can be activated in most other wikis. Some wiki engines such as <a href="/facts/TiddlyWiki/cJkD89qs">TiddlyWiki</a>, <a href="/facts/Trac/vYhkdoA3">Trac</a> and <a href="/facts/PmWiki/UaNEXF5k">PmWiki</a> make use of it in the default settings, but usually also provide a configuration mechanism or <a href="/facts/Plug-in_(computing)/351Du3Wu">plugin</a> to disable it. Wikipedia formerly used camel case linking as well, but switched to explicit link markup using <a href="/facts/Square_brackets/yzGM9J8A">square brackets</a><a class="footnote-ref" id="fnref:44" href="#fn:44"><sup>44</sup></a> and many other wiki sites have done the same. <a href="/facts/MediaWiki/MbkLUTor">MediaWiki</a>, for example, does not support camel case for linking. Some wikis that do not use camel case linking may still use the camel case as a naming convention, such as <a href="/facts/AboutUs/3yqJ6st5">AboutUs</a>. </p> <h3>Other uses</h3> <p>The <a href="/facts/National_Information_Exchange_Model/SaIRWkhK">NIEM</a> registry requires that <a href="/facts/XML/clNgUfWk">XML</a> data elements use upper camel case and XML attributes use lower camel case. </p><p>Most popular <a href="/facts/Command-line_interface/R9JpGmXQ">command-line interfaces</a> and <a href="/facts/Shell_script/NE7YvsBD">scripting</a> languages cannot easily handle file names that contain embedded spaces (usually requiring the name to be put in quotes). Therefore, users of those systems often resort to camel case (or underscores, hyphens and other "safe" characters) for compound file names like MyJobResume.pdf. </p><p><a href="/facts/Microblogging/f0QJUHt9">Microblogging</a> and <a href="/facts/Social_networking_service/qFIh6VT1">social networking services</a> that limit the number of characters in a message are potential outlets for medial capitals. Using camel case between words reduces the number of spaces, and thus the number of characters, in a given message, allowing more content to fit into the limited space. <a href="/facts/Hashtag/12P528G1">Hashtags</a>, especially long ones, often use camel case to maintain readability (e.g. #CollegeStudentProblems is easier to read than #collegestudentproblems);<a class="footnote-ref" id="fnref:45" href="#fn:45"><sup>45</sup></a> this practice improves <a href="/facts/Accessibility/hp9gz5GK">accessibility</a> as <a href="/facts/Screen_reader/Twune61n">screen readers</a> recognize CamelCase in parsing composite hashtags.<a class="footnote-ref" id="fnref:46" href="#fn:46"><sup>46</sup></a> </p><p>In website URLs, spaces are <a href="/facts/Percent-encoding/zprLw5se">percent-encoded</a> as "%20", making the address longer and less <a href="/facts/Human_readable/GDE1fpHT">human readable</a>. By omitting spaces, camel case does not have this problem. </p> <h2 id="readability-studies">Readability studies</h2> <p>Camel case has been criticized as negatively impacting readability due to the removal of spaces and uppercasing of every word.<a class="footnote-ref" id="fnref:47" href="#fn:47"><sup>47</sup></a> </p><p>A 2009 study of 135 subjects comparing <a href="/facts/Snake_case/jzdKQ6Wd">snake case</a> (underscored identifiers) to camel case found that camel case identifiers were recognized with higher accuracy among all subjects. Subjects recognized snake case identifiers more quickly than camel case identifiers. Training in camel case sped up camel case recognition and slowed snake case recognition, although this effect involved coefficients with high <a href="/facts/P-value/InnYd1bz">p-values</a>. The study also conducted a subjective survey and found that non-programmers either preferred underscores or had no preference, and 38% of programmers trained in camel case stated a preference for underscores. However, these preferences had no statistical correlation to accuracy or speed when controlling for other variables.<a class="footnote-ref" id="fnref:48" href="#fn:48"><sup>48</sup></a> </p><p>A 2010 follow-up study used a similar study design with 15 subjects consisting of expert programmers trained primarily in snake case. It used a static rather than animated stimulus and found perfect accuracy in both styles except for one incorrect camel case response. Subjects recognized identifiers in snake case more quickly than camel case. The study used eye-tracking equipment and found that the difference in speed for its subjects was primarily due to the fact that average duration of <a href="/facts/Fixation_(visual)/nnFUFcd9">fixations</a> for camel-case was significantly higher than that of snake case for 3-part identifiers. The survey recorded a mixture of preferred identifier styles but again there was no correlation of preferred style to accuracy or speed.<a class="footnote-ref" id="fnref:49" href="#fn:49"><sup>49</sup></a> </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/All_caps/ASFdydxp">All caps</a></li> <li><a href="/facts/Alternating_caps/mNxdohYI">Alternating caps</a></li> <li><a href="/facts/Capitalization/eJx3dTaq">Capitalization</a></li> <li><a href="/facts/Caps_lock/oWHJMrlx">Caps lock</a></li> <li><a href="/facts/Kebab_case/KQcwaUUD">Kebab case</a></li> <li><a href="/facts/Naming_convention_(programming)/4IVCWpSU">Naming convention (programming)</a></li> <li><a href="/facts/Sentence_case/KQcwaUUD">Sentence case</a></li> <li><a href="/facts/Shift_key/d0gXS7Jd">Shift key</a></li> <li><a href="/facts/Small_caps/SVH5prpT">Small caps</a></li> <li><a href="/facts/Snake_case/jzdKQ6Wd">Snake case</a></li> <li><a href="/facts/Title_case/vtY54sVw">Title case</a></li> <li><a href="/facts/Unicase/EgKIQzzf">Unicase</a></li></ul> <h2 id="external-links">External links</h2> Wikimedia Commons has media related to Camel case. Look up <i>camel case</i> in Wiktionary, the free dictionary. <ul><li><a href="https://camel-case.com">Camel Case Guide & Converter</a>, further reading on usage with examples</li> <li><a href="http://c2.com/cgi/wiki?CamelCase">Examples and history of CamelCase</a>, also <a href="http://c2.com/cgi/wiki?WordsSmashedTogetherLikeSo">WordsSmashedTogetherLikeSo</a></li> <li><a href="http://msdn2.microsoft.com/en-us/library/x2dbyw72(vs.71).aspx">.NET Framework General Reference Capitalization Styles</a></li> <li><a href="http://www.theslot.com/webnames.html">What's in a nAME(cq)?</a>, by Bill Walsh, at The Slot</li> <li><a href="http://www.microsoft.com/typography/ctfonts/WordRecognition.aspx">The Science of Word Recognition</a>, by Kevin Larson, Advanced Reading Technology, Microsoft Corporation</li> <li><a href="http://capitalizemytitle.com/camel-case/">Convert text to CamelCase</a></li> <li><a href="http://xml.coverpages.org/camelCase.html">OASIS Cover Pages: CamelCase for Naming XML-Related Components</a></li> <li><a href="https://titlecapitalize.com/text-to-camelcase/">Convert text to CamelCase, Title Case, Uppercase and lowercase</a></li> <li><a href="https://medium.com/@shahnazi2002/demystifying-common-casings-in-programming-what-they-are-and-when-to-use-them-efbd8c1ec2a0">Demystifying Common Casings in Programming: What They Are and When to Use Them</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Fogarty, Mignon (27 October 2009). The Grammar Devotional: Daily Tips for Successful Writing from Grammar Girl. St. Martin's Publishing Group. p. 14. ISBN 978-1-4299-6440-1. <a href="978-1-4299-6440-1" target="_blank">978-1-4299-6440-1</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Brown, Adam (21 September 2018). Understanding and Teaching English Spelling: A Strategic Guide. Routledge. pp. 173–174. ISBN 978-1-351-62186-1. <a href="978-1-351-62186-1" target="_blank">978-1-351-62186-1</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Dreyer, Benjamin (4 August 2020). Dreyer's English: An Utterly Correct Guide to Clarity and Style. Random House Publishing Group. p. 228. ISBN 978-0-8129-8571-9. <a href="978-0-8129-8571-9" target="_blank">978-0-8129-8571-9</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"Capitalization Styles - .NET Framework 1.1". 17 November 2006. Retrieved 5 December 2012. <a href="http://msdn.microsoft.com/en-us/library/x2dbyw72(v=vs.71).aspx" target="_blank">http://msdn.microsoft.com/en-us/library/x2dbyw72(v=vs.71).aspx</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"Naming Conventions". Scala. Retrieved 5 December 2012. <a href="http://docs.scala-lang.org/style/naming-conventions.html" target="_blank">http://docs.scala-lang.org/style/naming-conventions.html</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"Capitalization Styles - .NET Framework 1.1". 17 November 2006. Retrieved 5 December 2012. <a href="http://msdn.microsoft.com/en-us/library/x2dbyw72(v=vs.71).aspx" target="_blank">http://msdn.microsoft.com/en-us/library/x2dbyw72(v=vs.71).aspx</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"Camel Case". Retrieved 10 March 2016. <a href="http://c2.com/cgi/wiki?CamelCase" target="_blank">http://c2.com/cgi/wiki?CamelCase</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"Ada 95 Quality and Style Guide". October 1995. Section 3.1.3. Retrieved 25 January 2020. <a href="https://www.adaic.org/resources/add_content/docs/95style/html/sec_3/3-1-3.html" target="_blank">https://www.adaic.org/resources/add_content/docs/95style/html/sec_3/3-1-3.html</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>C# Coding Standards and Guidelines Archived 11 April 2008 at the Wayback Machine at Purdue University College of Technology <a href="http://www2.tech.purdue.edu/cit/Courses/CPT355/C_Sharp_Coding_Standards_and_Guidelines.asp" target="_blank">http://www2.tech.purdue.edu/cit/Courses/CPT355/C_Sharp_Coding_Standards_and_Guidelines.asp</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>"CamelCase@Everything2.com". Everything2.com. Retrieved 4 June 2010. <a href="http://everything2.com/title/CamelCase" target="_blank">http://everything2.com/title/CamelCase</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>Style Guide for Python Code at www.python.org <a href="http://legacy.python.org/dev/peps/pep-0008/" target="_blank">http://legacy.python.org/dev/peps/pep-0008/</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>Feldman, Ian (29 March 1990). "compoundNames". Newsgroup: alt.folklore.computers. Usenet: 3230@draken.nada.kth.se. <a href="https://groups.google.com/group/alt.folklore.computers/browse_thread/thread/6099191f2c4e0984/21f332e5b813313e?#21f332e5b813313e" target="_blank">https://groups.google.com/group/alt.folklore.computers/browse_thread/thread/6099191f2c4e0984/21f332e5b813313e?#21f332e5b813313e</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>"[#APF-1088] If class name has embedded capitals, AppGen code fails UI tests and generated hyperlinks are incorrect. – AppFuse JIRA". Issues.appfuse.org. Archived from the original on 25 June 2017. Retrieved 4 June 2010. <a href="https://web.archive.org/web/20170625073321/http://issues.appfuse.org/browse/APF-1088" target="_blank">https://web.archive.org/web/20170625073321/http://issues.appfuse.org/browse/APF-1088</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>ASP Naming Conventions Archived 8 April 2009 at the Wayback Machine, by Nannette Thacker (05/01/1999) <a href="http://www.shiningstar.net/articles/articles/standards/namingconventions.asp" target="_blank">http://www.shiningstar.net/articles/articles/standards/namingconventions.asp</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>Iverson, Cheryl; Christiansen, Stacy; Flanagin, Annette; Fontanarosa, Phil B.; Glass, Richard M.; Gregoline, Brenda; Lurie, Stephen J.; Meyer, Harriet S.; Winker, Margaret A.; Young, Rozanne K., eds. (2007). AMA Manual of Style (10th ed.). Oxford, Oxfordshire: Oxford University Press. ISBN 978-0-19-517633-9. <a href="978-0-19-517633-9" target="_blank">978-0-19-517633-9</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> <li id="fn:16"><p>Hult, Christine A.; Huckin, Thomas N. "The Brief New Century Handbook – Rules for internal capitalization". Pearson Education. Archived from the original on 7 April 2012. <a href="https://web.archive.org/web/20120407020530/http://wps.ablongman.com/long_hult_bnch_4/63/16207/4149058.cw/content/index.html" target="_blank">https://web.archive.org/web/20120407020530/http://wps.ablongman.com/long_hult_bnch_4/63/16207/4149058.cw/content/index.html</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></p></li> <li id="fn:17"><p>"What is the name for a word containing two capital letters (like WordPad)?". AskOxford. Internet Archive. Archived from the original on 25 October 2008. Retrieved 12 June 2022. <a href="https://web.archive.org/web/20081025021810/http://www.askoxford.com/asktheexperts/faq/aboutwords/medial?view=uk" target="_blank">https://web.archive.org/web/20081025021810/http://www.askoxford.com/asktheexperts/faq/aboutwords/medial?view=uk</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></p></li> <li id="fn:18"><p>Style Guide for Python Code at www.python.org <a href="http://legacy.python.org/dev/peps/pep-0008/" target="_blank">http://legacy.python.org/dev/peps/pep-0008/</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></p></li> <li id="fn:19"><p>"Brad Abrams: History around Pascal Casing and Camel Casing". learn.microsoft.com. 3 February 2004. Retrieved 21 October 2024. <a href="https://learn.microsoft.com/en-us/archive/blogs/brada/history-around-pascal-casing-and-camel-casing" target="_blank">https://learn.microsoft.com/en-us/archive/blogs/brada/history-around-pascal-casing-and-camel-casing</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></p></li> <li id="fn:20"><p>"Pascal Case". C2.com. 27 September 2012. Retrieved 4 January 2014. <a href="http://c2.com/cgi/wiki?PascalCase" target="_blank">http://c2.com/cgi/wiki?PascalCase</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></p></li> <li id="fn:21"><p>"NET Framework General Reference Capitalization Styles". MSDN2. 17 November 2006. Retrieved 4 January 2014. <a href="http://msdn2.microsoft.com/en-us/library/x2dbyw72(vs.71).aspx" target="_blank">http://msdn2.microsoft.com/en-us/library/x2dbyw72(vs.71).aspx</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></p></li> <li id="fn:22"><p>"WikiWord". Twiki.org. Archived from the original on 19 June 2010. Retrieved 4 June 2010. <a href="https://web.archive.org/web/20100619042605/http://twiki.org/cgi-bin/view/TWiki/WikiWord" target="_blank">https://web.archive.org/web/20100619042605/http://twiki.org/cgi-bin/view/TWiki/WikiWord</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></p></li> <li id="fn:23"><p>"Wiki Case". C2.com. 8 February 2010. Retrieved 4 June 2010. <a href="http://c2.com/cgi/wiki?WikiCase" target="_blank">http://c2.com/cgi/wiki?WikiCase</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></p></li> <li id="fn:24"><p>Rappoport, Avi (3 April 1990). "compoundNames". Newsgroup: alt.folklore.computers. <a href="https://groups.google.com/g/alt.folklore.computers/c/YJkZHyxOCYQ/m/PjETuOUy8yEJ" target="_blank">https://groups.google.com/g/alt.folklore.computers/c/YJkZHyxOCYQ/m/PjETuOUy8yEJ</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></p></li> <li id="fn:25"><p>Newton Love (12 September 1995). "I'm happy again! – comp.os.os2.advocacy | Google Groups". Groups.google.com. Retrieved 23 May 2009. <a href="https://groups.google.com/group/comp.os.os2.advocacy/msg/ab3c8107c6e150fa" target="_blank">https://groups.google.com/group/comp.os.os2.advocacy/msg/ab3c8107c6e150fa</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></p></li> <li id="fn:26"><p>"Newton Love". Saint Louis Unix Users Group.[dead link] <a href="http://sluug.org/~newt/" target="_blank">http://sluug.org/~newt/</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></p></li> <li id="fn:27"><p>Abrams, Brad (3 February 2004). "History around Pascal Casing and Camel Casing". learn.microsoft.com. Retrieved 1 February 2025. <a href="https://learn.microsoft.com/sv-se/archive/blogs/brada/history-around-pascal-casing-and-camel-casing" target="_blank">https://learn.microsoft.com/sv-se/archive/blogs/brada/history-around-pascal-casing-and-camel-casing</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></p></li> <li id="fn:28"><p>Richtiges und gutes Deutsch: Das Wörterbuch der sprachlichen Zweifelsfälle. Duden (in German). Vol. 9 (7th ed.). Mannheim: Bibliographisches Institut. 2011. p. 418. ISBN 978-3411040971. <a href="978-3411040971" target="_blank">978-3411040971</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></p></li> <li id="fn:29"><p>Fowler, Henry W.; Fowler, Francis G. (1908). "Chapter IV. Punctuation – Hyphens". The King's English (2nd ed.). Oxford. Archived from the original on 31 December 2009. Retrieved 19 December 2009. <a href="/wiki/Henry_Watson_Fowler" target="_blank">/wiki/Henry_Watson_Fowler</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></p></li> <li id="fn:30"><p>Jöns Jacob Berzelius (1813). Essay on the Cause of Chemical Proportions and on Some Circumstances Relating to Them: Together with a Short and Easy Method of Expressing Them. Annals of Philosophy 2, 443-454, 3, 51-52; (1814) 93-106, 244-255, 353-364. <a href="/wiki/J%C3%B6ns_Jacob_Berzelius" target="_blank">/wiki/J%C3%B6ns_Jacob_Berzelius</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></p></li> <li id="fn:31"><p>Henry M. Leicester & Herbert S. Klickstein, eds. 1952, A Source Book in Chemistry, 1400-1900 (Cambridge, MA: Harvard) <a href="/wiki/Henry_M._Leicester" target="_blank">/wiki/Henry_M._Leicester</a> <a href="#fnref:31" class="footnote-back-ref">↩</a></p></li> <li id="fn:32"><p>The Trade-mark Reporter. United States Trademark Association. 1930. ISBN 1-59888-091-8. {{cite book}}: ISBN / Date incompatibility (help) <a href="1-59888-091-8" target="_blank">1-59888-091-8</a> <a href="#fnref:32" class="footnote-back-ref">↩</a></p></li> <li id="fn:33"><p>"Mister Rogers Neighborhood Season 1 (Episode 4)". Retrieved 21 June 2022. <a href="https://archive.org/details/mister-rogers-neighborhood-season-01/004.mp4" target="_blank">https://archive.org/details/mister-rogers-neighborhood-season-01/004.mp4</a> <a href="#fnref:33" class="footnote-back-ref">↩</a></p></li> <li id="fn:34"><p>"Our History". unitedhealthgroup.com. Archived from the original on 1 May 2019. Retrieved 15 May 2019. <a href="https://web.archive.org/web/20190501121118/http://www.unitedhealthgroup.com/about/history.html" target="_blank">https://web.archive.org/web/20190501121118/http://www.unitedhealthgroup.com/about/history.html</a> <a href="#fnref:34" class="footnote-back-ref">↩</a></p></li> <li id="fn:35"><p>""Resume of Session 8". Digital Computers: Advanced Coding Techniques. Summer Session 1954, Massachusetts Institute of Technology" (PDF). 1954. pp. 8–6. Archived from the original (PDF) on 29 February 2012. Retrieved 4 January 2014. <a href="https://web.archive.org/web/20120229201504/http://bitsavers.org/pdf/mit/summer_session_1954/Digital_Computers_Advanced_Coding_Techniques_Summer_1954.pdf" target="_blank">https://web.archive.org/web/20120229201504/http://bitsavers.org/pdf/mit/summer_session_1954/Digital_Computers_Advanced_Coding_Techniques_Summer_1954.pdf</a> <a href="#fnref:35" class="footnote-back-ref">↩</a></p></li> <li id="fn:36"><p>Strachey, Christopher (October 1965). "A General Purpose Macrogenerator". Computer Journal. 8 (3): 225–241. doi:10.1093/comjnl/8.3.225. <a href="/wiki/Christopher_Strachey" target="_blank">/wiki/Christopher_Strachey</a> <a href="#fnref:36" class="footnote-back-ref">↩</a></p></li> <li id="fn:37"><p>Niklaus Wirth (2007). "Modula-2 and Oberon". Proceedings of the third ACM SIGPLAN conference on History of programming languages. HOPL III - San Diego. pp. 3-1 – 3-10. CiteSeerX 10.1.1.91.1447. doi:10.1145/1238844.1238847. ISBN 9781595937667. S2CID 1918928. <a href="9781595937667" target="_blank">9781595937667</a> <a href="#fnref:37" class="footnote-back-ref">↩</a></p></li> <li id="fn:38"><p>wwlpublish. "Declare variables - Training". learn.microsoft.com. Retrieved 29 August 2023. <a href="https://learn.microsoft.com/en-us/training/modules/csharp-literals-variables/3-declaring-variables" target="_blank">https://learn.microsoft.com/en-us/training/modules/csharp-literals-variables/3-declaring-variables</a> <a href="#fnref:38" class="footnote-back-ref">↩</a></p></li> <li id="fn:39"><p>Farhad Manjoo (30 April 2002). "Grads Want to Study on EMacs, Too". Wired.com. Retrieved 4 June 2010. <a href="https://www.wired.com/science/discoveries/news/2002/04/52181" target="_blank">https://www.wired.com/science/discoveries/news/2002/04/52181</a> <a href="#fnref:39" class="footnote-back-ref">↩</a></p></li> <li id="fn:40"><p>Feedback, 20 June 1998 Vol 158 No 2139 New Scientist 20 June 1998 <a href="https://www.newscientist.com/article/mg15821399.900-feedback.html" target="_blank">https://www.newscientist.com/article/mg15821399.900-feedback.html</a> <a href="#fnref:40" class="footnote-back-ref">↩</a></p></li> <li id="fn:41"><p>"Google Java Style Guide". google.github.io. Retrieved 2 November 2022. <a href="https://google.github.io/styleguide/javaguide.html#s5.3-camel-case" target="_blank">https://google.github.io/styleguide/javaguide.html#s5.3-camel-case</a> <a href="#fnref:41" class="footnote-back-ref">↩</a></p></li> <li id="fn:42"><p>Dave Binkley; Marcia Davis; Dawn Lawrie; Christopher Morrell (2009). "To CamelCase or Under_score". IEEE 17th International Conference on Program Comprehension, 2009. ICPC '09. IEEE: 158–167. CiteSeerX 10.1.1.158.9499. In terms of camel-cased identifiers, this has a greater impact on identifiers that include short words and especially acronyms. For example, consider the acronym ID found in the identifier kIOuterIIDPath. Because of the run of uppercase letters, the task of reading kIOuterIIDPath, in particular the identification of the word ID, is more difficult. <a href="/wiki/CiteSeerX_(identifier)" target="_blank">/wiki/CiteSeerX_(identifier)</a> <a href="#fnref:42" class="footnote-back-ref">↩</a></p></li> <li id="fn:43"><p>Andrew Lih, The Wikipedia Revolution: How a Bunch of Nobodies Created the World's Greatest Encyclopedia (New York: Hyperion, 2009), pp. 57–58. <a href="#fnref:43" class="footnote-back-ref">↩</a></p></li> <li id="fn:44"><p>Lih, The Wikipedia Revolution, pp. 62–63, 67. <a href="#fnref:44" class="footnote-back-ref">↩</a></p></li> <li id="fn:45"><p>Blackwood, Jessica; Brown, Kate. "Accessible Use of CamelCase and Structuring Posts". <a href="https://ecampusontario.pressbooks.pub/accessibledigitalcontenttraining/chapter/accessible-use-of-camelcase-and-structuring-posts/" target="_blank">https://ecampusontario.pressbooks.pub/accessibledigitalcontenttraining/chapter/accessible-use-of-camelcase-and-structuring-posts/</a> <a href="#fnref:45" class="footnote-back-ref">↩</a></p></li> <li id="fn:46"><p>"Social Media Accessibility Guidelines". Archived from the original on 12 October 2022. Retrieved 12 October 2022. <a href="https://web.archive.org/web/20221012082805/https://accessibility.princeton.edu/guidelines/social-media#camelcase" target="_blank">https://web.archive.org/web/20221012082805/https://accessibility.princeton.edu/guidelines/social-media#camelcase</a> <a href="#fnref:46" class="footnote-back-ref">↩</a></p></li> <li id="fn:47"><p>Caleb Crain (23 November 2009). "Against Camel Case". New York Times. <a href="https://www.nytimes.com/2009/11/29/magazine/29FOB-onlanguage-t.html?_r=2&ref=magazine&" target="_blank">https://www.nytimes.com/2009/11/29/magazine/29FOB-onlanguage-t.html?_r=2&ref=magazine&</a> <a href="#fnref:47" class="footnote-back-ref">↩</a></p></li> <li id="fn:48"><p>Dave Binkley; Marcia Davis; Dawn Lawrie; Christopher Morrell (2009). "To CamelCase or Under_score". IEEE 17th International Conference on Program Comprehension, 2009. ICPC '09. IEEE: 158–167. CiteSeerX 10.1.1.158.9499. The experiment builds on past work of others who study how readers of natural language perform such tasks. Results indicate that camel casing leads to higher accuracy among all subjects regardless of training, and those trained in camel casing are able to recognize identifiers in the camel case style faster than identifiers in the underscore style. <a href="/wiki/CiteSeerX_(identifier)" target="_blank">/wiki/CiteSeerX_(identifier)</a> <a href="#fnref:48" class="footnote-back-ref">↩</a></p></li> <li id="fn:49"><p>Bonita Sharif; Jonathan I. Maletic (2010). "An Eye Tracking Study on camelCase and under_score Identifier Styles". 2010 IEEE 18th International Conference on Program Comprehension. IEEE. pp. 196–205. CiteSeerX 10.1.1.421.6137. doi:10.1109/ICPC.2010.41. ISBN 978-1-4244-7604-6. S2CID 14170019. (download PDF). An empirical study to determine if identifier-naming conventions (i.e., camelCase and under_score) affect code comprehension is presented. An eye tracker is used to capture quantitative data from human subjects during an experiment. The intent of this study is to replicate a previous study published at ICPC 2009 (Binkley et al.) that used a timed response test method to acquire data. The use of eye-tracking equipment gives additional insight and overcomes some limitations of traditional data gathering techniques. Similarities and differences between the two studies are discussed. One main difference is that subjects were trained mainly in the underscore style and were all programmers. While results indicate no difference in accuracy between the two styles, subjects recognize identifiers in the underscore style more quickly. <a href="978-1-4244-7604-6" target="_blank">978-1-4244-7604-6</a> <a href="#fnref:49" class="footnote-back-ref">↩</a></p></li> </ol>