-
Notifications
You must be signed in to change notification settings - Fork 1
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
change C APIs names #58
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a mix of standards, some variables have upper case, underscore and camel case. Typically the standard is:
Functions & local variables: all lower case and separated by "_"
Classes: Camel case
Global Variables: Upper case and separated by "_"
The standard used here is <interfacename>_<function named Camel case > |
@@ -90,7 +90,7 @@ void bb_configure_2_gpios(unsigned int configL,unsigned int configR){ | |||
} | |||
} | |||
|
|||
void bb_configure_all_gpios(unsigned int config){ | |||
void bb_configureAllGpios(unsigned int config){ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example here it's a mix of "_" and camel case
It's okay to comeup with a standard for your code, but it's important to keep it consistent, for example; if the |
No description provided.