From ce0b334a5fadb5e48143b42db6e60820e41771fe Mon Sep 17 00:00:00 2001 From: Anton Curmanschii Date: Mon, 11 Mar 2024 22:16:18 +0200 Subject: [PATCH] Rephrase a few things for better reading experience --- raylib-coding-conventions.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/raylib-coding-conventions.md b/raylib-coding-conventions.md index d158db0..907a47c 100644 --- a/raylib-coding-conventions.md +++ b/raylib-coding-conventions.md @@ -25,7 +25,7 @@ Some other conventions to follow: - 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 if (condition) value = 0; @@ -46,7 +46,7 @@ switch (value) 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 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 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.**