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

fix naming conventions #43

Open
SwadicalRag opened this issue May 15, 2017 · 2 comments
Open

fix naming conventions #43

SwadicalRag opened this issue May 15, 2017 · 2 comments

Comments

@SwadicalRag
Copy link
Member

The exposed C++<->Lua api is fairly consistent, but the pure Lua API is messy as fuck.

Here's how I'm doing it:

  • local vars are simpleCaseCamelCased
  • global vars are UpperCaseCamelCased, with the exception of gm_voxelate
  • class methods are UpperCaseCamelCased
  • avoid using snake_case because it looks weird af tbh

Thoughts @birdbrainswagtrain ?

@MDFL64
Copy link
Member

MDFL64 commented May 15, 2017

Sounds good to me. I have some additional minor name changes that I might make to the lua API. I also might continue using sexy_snake_case for locals because that's how I roll.

@SwadicalRag
Copy link
Member Author

all good as long as the exposed API is consistent :v

@MDFL64 MDFL64 modified the milestone: 0.4.0 Jun 8, 2017
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