Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide naming convention for symbol names containing abbreviations (XmlRpcCall [A] vs. XMLRPCCall [B]) #761

Open
Stinkfist0 opened this issue Apr 16, 2014 · 1 comment

Comments

@Stinkfist0
Copy link
Contributor

Personally I'd vote for the [A] convention:

  1. When there are lots of contiguous abbreviations in a symbol name, deciphering a symbol name written using [B] requires a priori knowledge of the abbreviations,
  2. personal preference ("looks clearer and better"),
  3. Qt uses it (f.ex. QUdpSocket),
  4. [B] can lead to all uppercase names which is not nice (f.ex. UIAPI) and can be mixed with preprocessor defines.

Preferably use the same convention for both Tundra, WebTundra. FWIW, currently I could find at least four different styles currently in the code base: A (HttpAssetProvider), B (SaveSceneXML), mixed (UiAPI), and even something else (DecompressCRNtoDDS).

@jonnenauha
Copy link
Member

I think AssetApi etc would just feel wrong if we were to change it :) I like B better but have to mix it up sometimes, like SaveSceneXML looks good but DecompressCRNToDDS and DecompressCrnToDds look bad.

I would stick with upper case with possibility to override if something else looks better :P Kind of a meh topic tbh :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants