CamelCase (Portuguese Wikipedia)

Analysis of information sources in references of the Wikipedia article "CamelCase" in Portuguese language version.

refsWebsite
Global rank Portuguese rank
5,959th place
9,259th place
153rd place
178th place
low place
low place
3,959th place
3,028th place
8,400th place
4,384th place
2,069th place
47th place
low place
low place
low place
low place
7,231st place
8,980th place
6,359th place
4,735th place
2,232nd place
2,242nd place
low place
low place
low place
low place
low place
low place
207th place
589th place
652nd place
920th place
9,450th place
low place

americanscientist.org

appfuse.org

issues.appfuse.org

c2.com

wiki.c2.com

catb.org

  • Catb. «camelCase» (em inglês). Consultado em 8 de janeiro de 2013 

computerhope.com

  • Computer Hope. «CamelCase» (em inglês). Consultado em 8 de janeiro de 2013 

everything2.com

freecodecamp.org

ieee.org

ieeexplore.ieee.org

  • Bonita Sharif and Jonathan I. Maletic (2010). "An Eye Tracking Study on camelCase and under_score Identifier Styles"IEEE 18th International Conference on Program Comprehension, 20010. ICPC '10. IEEE: 196–205. (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.

kent.edu

cs.kent.edu

  • Bonita Sharif and Jonathan I. Maletic (2010). "An Eye Tracking Study on camelCase and under_score Identifier Styles"IEEE 18th International Conference on Program Comprehension, 20010. ICPC '10. IEEE: 196–205. (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.

microsoft.com

msdn.microsoft.com

blogs.msdn.microsoft.com

psu.edu

citeseerx.ist.psu.edu

  • Dave Binkley and Marcia Davis and Dawn Lawrie and 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.

python.org

legacy.python.org

scala-lang.org

docs.scala-lang.org

shiningstar.net

twiki.org

usp.br

www2.icmc.usp.br

xbrl.org.au