twix/raylib
1
0
Fork 0
mirror of https://github.com/raysan5/raylib.git synced 2026-02-02 04:09:18 -05:00
Code Issues Packages Projects Releases Wiki Activity

Rephrase a few things for better reading experience

Anton Curmanschii
2024-03-11 22:16:18 +02:00
parent 8d2487f232
commit ce0b334a5f
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
raylib-coding-conventions.md

@ -25,7 +25,7 @@ Some other conventions to follow:
- raylib code does not use TABS, use 4 spaces instead. - raylib code does not use TABS, use 4 spaces instead.
- Control flow statements always are followed by a space: - Control flow statements are always followed by a space:
```c ```c
if (condition) value = 0; if (condition) value = 0;
@ -46,7 +46,7 @@ switch (value)
default: break; default: break;
} }
``` ```
- All conditions checks are always between parenthesis but not boolean values: - All condition checks are always encoled in parentheses, with the exception of simple boolean values:
```c ```c
if ( (value > 1) && (value < 50) && valueActive ) if ( (value > 1) && (value < 50) && valueActive )
{ {
@ -54,7 +54,7 @@ if ( (value > 1) && (value < 50) && valueActive )
} }
``` ```
- When dealing with braces or curly brackets, open-close them in aligned mode, it's more visual for students: - When dealing with curly braces, open-close them in aligned mode, it's more visual for students:
```c ```c
void SomeFunction() void SomeFunction()
{ {
@ -62,4 +62,4 @@ void SomeFunction()
} }
``` ```
**When proposing new functions, please try to use a clear naming for function-name and functions-parameters, in case of doubt, open an issue for discussion.** **When proposing new functions, please try to use a clear naming for function-name and function-parameters. In case of doubt, open an issue for discussion.**