You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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,
personal preference ("looks clearer and better"),
Qt uses it (f.ex. QUdpSocket),
[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).
The text was updated successfully, but these errors were encountered:
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 :)
Personally I'd vote for the [A] convention:
QUdpSocket
),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
).The text was updated successfully, but these errors were encountered: