0

I just wonder why Google is using in API client libraries such UglyCase method names instead of existing_coding_standards? Actually, I am not happy to mess my PEP8 code with something like this (GetEditLink() ...wtf? class name?).

Josh Lee
  • 171,072
  • 38
  • 269
  • 275
Honza Javorek
  • 8,566
  • 8
  • 47
  • 66
  • Maybe you should ask them! :) – Simone May 06 '11 at 12:51
  • 2
    Because they like it better, that's the only reason for any details of any coding standard ever. – Cat Plus Plus May 06 '11 at 12:52
  • 3
    FWIW that example `GetEditLink()` violates [Google's own Python styleguide](http://google-styleguide.googlecode.com/svn/trunk/pyguide.html), so I'm guessing that because the API exists in many languages and they had to use the most common naming schemes. – samplebias May 06 '11 at 12:55
  • @samplebias: Yes, this style is recommended in their C++ guidelines. It's hideous in either language, but at least it's consistent. – Fred Foo May 06 '11 at 12:57
  • AFAIK all their API libraries look like that. I really don't like it. Every language has it's own customs and conventions and they ignore it. If they wanted a common style across many languages, they could probably also finish every line of code by `;`. – Honza Javorek May 06 '11 at 12:58
  • See the answers to http://stackoverflow.com/questions/159720/what-is-the-naming-convention-in-python-for-variable-and-function-names – Petr Viktorin May 06 '11 at 13:40

1 Answers1

3

Well, quoting the PEP8 Code:

mixedCase is allowed only in contexts where that's already the prevailing style (e.g. threading.py), to retain backwards compatibility.

So either that, or they just like it better.

Herman Schaaf
  • 46,821
  • 21
  • 100
  • 139